How to prevent nested node_modules inside node_modules

npm npm-install node-modules
Jacoslaw picture Jacoslaw · Aug 10, 2018 · Viewed 7.7k times · Source

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?

Answer

Md. Abu Taher picture Md. Abu Taher · Aug 10, 2018

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.

Related questions

How to install an npm package from GitHub directly?

Trying to install modules from github results in: ENOENT error on package.json. Easily reproduced using express: npm install https://github.com/visionmedia/express throws error. npm install express works. Why can't I install from github? Here is the console …

Read More
How to fix 'fs: re-evaluating native module sources is not supported' - graceful-fs

Recently I've made a switch to Node v.6, and It started creating more and more problems with running normal builds grunt/gulp/webpack For example: $ gulp [14:02:20] Local gulp not found in ~/_Other/angular-2-ts/angular2-seed [14:02:20] Try running: npm install …

Read More
How does NPM handle version conflicts?

Since NPM version 3 node modules and dependencies are all installed at the same root level. But what if I install two modules that depend on two different versions of the same module? For instance, if I install async npm i …

Read More