What's the correct way to handle packages version

[ndozhh]

Hello everyone!

I'm facing a problem again with duplicated versions of some packages. As you can see there two versions of the same package in my dependencies:

But the thing is I have the version of each package fixed in my package.json:

If I go to the package-lock.json, some internal packages inside @react-aria are pointing to the latest (I think) version of the package

I know there's a problem because right now my tooltips are not working because the double version of @react-aria/utils and in the past I fixed the same problem updating to the latest version of each package, but what if I don't want to update again now but do it in the future?

Is there anything I can do here to not have duplicated versions?

Thank you!!

[snowystinger]

Hi, thanks for the discussion.

NPM (and other package managers) can try to be a little too smart when it comes to frontend, and it will frequently try to install multiple copies of packages so as to introduce the fewest code path changes possible. This is great for servers, however, for client code, it's usually unwanted.

You may need to use tools like dedupe or resolutions in order to get back to a single copy of a given package. Another option, you could delete just the entries in your lock file, but make sure you delete node_modules as when the reinstall takes place, if you have any node_modules locally, it will try to use those to resolve so it installs faster. You can also delete node_modules and your entire lock file for the nuclear option.

[ndozhh]

Thank you very much @snowystinger

I ended up using npm overrides and it's working now.