Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to prevent nested node_modules inside node_modules

Tags:

I've created my own npm package, let's call it XYZ, it has @material-ui dependency in it's package.json file.

When I install it in project A I have nested node_modules inside of XYZ folder(so it's A\node_modules\XYZ\node_modules\@material-ui), but when I install it in project B I don't have nested node_modules folder. Both project A and B has @material-ui in their package.json files with same versions.

How to force my XYZ package to use @material-ui from A\node_modules?

like image 463
Jac Mos Avatar asked Aug 10 '18 12:08

Jac Mos


People also ask

How do I remove npm nested dependency?

If you're using npm : Run npm dedupe after installing packages to remove nested duplicates. You can try deleting your package-lock. json and do a fresh install.

What is .staging folder in node_modules?

While doing npm install, inside node_modules . staging folder is getting created. Reasons: This is a temporary folder where the modules will be kept untill npm downloads all the modules specified in the package.

Should node_modules be committed?

They are no longer recommending the node_modules folder be committed. Usually, no. Allow npm to resolve dependencies for your packages.

Does npm CI remove node_modules?

npm ci will do the following things: It will delete your node_modules folder to ensure a clean state. It will look in your package-lock.


2 Answers

There are upside of having less nested folders and downside having more folders in node_modules folder directly and version control problems.

Use correct npm version

Correct yarn and npm (ie: npm v3) should not have such structure issue. It should always flatten the whole structure where possible and only have nested node_modules if the versions are incompatible with the one at top.

Check versions

So if you have it working properly on one project and not on another, its probably due to version. Check out if the @material-ui is same version on both. Maybe two different packages are conflicting with each other at some point.

Check how you are installing them

From your question, it says it's same version. However, you did not mention how you installed your package on both project. If you install with yarn link or npm link it should install dependencies properly as expected.

Check if you are using different packages

If you check the package, recently material-ui has been deprecated, and the notice says to upgrade to @material-ui/core instead. It might be some packages inside that folder is not same. Either way, it's like this whenever there is some dependency conflict. Check inside the @material-ui folder.

Flatten them manually (dangerous)

There are several packages to forcefully resolve this issue. They will go thru the nested node_modules folders and flatten them into single folder.

flatten-packages

  • Install with, npm install -g flatten-packages.
  • Run executable flatten-packages to rearrange all packages in node_modules folder in the project directory.
  • Flatten will delete older version of a package. You should take care of version breaking changes related errors.
like image 190
Md. Abu Taher Avatar answered Oct 12 '22 08:10

Md. Abu Taher


You can use npm dedupe command to accomplish this.

You can put the command in postinstall script in package.json, and every time NPM installs package, the npm dedupe command will flatten all the duplicated packages in same version for you.

For more information, see https://docs.npmjs.com/cli/dedupe

npm postinstall script

like image 30
RaynorChan Avatar answered Oct 12 '22 07:10

RaynorChan