4

I've installed most of the NPM modules globally with -g

However, I see that whenever I create a new app project (example: angular project) using Yeoman, I see that the npm modules get downloaded again and get installed in the local node_modules folder.

I consider that this is extremely wasteful that the same modules gets downloaded and copied for each new project. The size of each new project is then around 160MB.

Is there a way to download only the modules locally in the new project that are not already available in the global npm node_modules folder? Say, anyway to automatically create symbolic links from the local node_modules folder to the globally installed npm modules?

Is this possible? How to set it up?

muraliv
  • 169
  • 1
  • 7
  • LOL. Same here.... although I am quite experienced , this npm (and maven in Java) is really a pain, the time spent on that is more than developing the app itself – Phung D. An Mar 04 '15 at 23:14
  • You might have a look at my answer on **[“Self Referencing Loop Detected” exception with JSON.Net](https://stackoverflow.com/questions/40472419/self-referencing-loop-detected-exception-with-json-net/51235783#51235783)** page. – Murat Yıldız Jul 08 '18 at 20:34

2 Answers2

1

This is actually by design. From the Node.js blog:

In general, the rule of thumb is:

1.If you’re installing something that you want to use in your program, using require('whatever'), then install it locally, at the root of your project.

2.If you’re installing something that you want to use in your shell, on the command line or something, install it globally, so that its binaries end up in your PATH environment variable.

it is important for you to install project dependencies locally, as you have no guarantee that what is installed globally on your machine may be available on the deployment machine. True, you may manage both machines, or they may in fact be the same machine, but that case is never guaranteed.

Also, it's not unusual for you to have projects which rely upon a specific version of an npm which you may have installed an update for globally, breaking the project that needed the older version. Isolation is a key to keeping projects functional.

if you REALLY need to only maintain one copy, you can use symlinks. npm link globalnpm

Install it globally, and then npm link coffee-script or npm link express (if you’re on a platform that supports symbolic links.) Then you only need to update the global copy to update all the symlinks as well.

Note that the symlink option is really only relevant for hand initialized projects; generators such as Yeoman will always use local, as they follow the grain.

Community
  • 1
  • 1
Claies
  • 22,124
  • 4
  • 53
  • 77
  • 1
    Also note that npm **does not** download fresh copies of modules every time you install. It maintains a [local cache](https://www.npmjs.org/doc/cli/npm-cache.html) and copies the files from there. (It does ping the registry during installation to check for updated versions, however. This is a very small request.) – josh3736 Dec 02 '14 at 23:48
0

There are workarounds, but this is intentional to avoid equivalent to DLL hell or specifically library versioning mismatch meltdown. Besides 160 MB is a tiny price to pay for this luxury. Discrete functioning bundles are much nicer to ship as a unit of goodness - trust me

Scott Stensland
  • 26,870
  • 12
  • 93
  • 104