How can I make multiple projects share node_modules directory?
node.jsNpmnode.js Problem Overview
Whenever I make projects, I have to download all dependencies of node modules. Without copying the node_modules, Is there anyway to share the central node_modules in multiple projects?
like the followings, I have to run many commands every time..
npm install gulp-usemin
npm install gulp-wrap
npm install gulp-connect
npm install gulp-watch
npm install gulp-minify-css
npm install gulp-uglify
npm install gulp-concat
npm install gulp-less
npm install gulp-rename
npm install gulp-minify-html
node.js Solutions
Solution 1 - node.js
You absolutely can share a node_modules directory amongst projects.
From node's documentation:
> If the module identifier passed to require() is not a native module, > and does not begin with '/', '../', or './', then node starts at the > parent directory of the current module, and adds /node_modules, and > attempts to load the module from that location. > > If it is not found there, then it moves to the parent directory, and > so on, until the root of the file system is reached. > > For example, if the file at '/home/ry/projects/foo.js' called > require('bar.js'), then node would look in the following locations, in > this order: > > /home/ry/projects/node_modules/bar.js /home/ry/node_modules/bar.js > /home/node_modules/bar.js /node_modules/bar.js
So just put a node_modules folder inside your projects directory and put in whatever modules you want. Just require them like normal. When node doesn't find a node_modules directory in your project folder, it will check the parent folder automatically. So make your directory structure like this:
-myProjects
--node_modules
--myproject1
---sub-project
--myproject2
So like this, even your sub-project's dependencies can draw on your main node_modules repository.
One drawback to doing it this way is you will have to build out your package.json file manually (unless someone knows a way to automate this with grunt or something). When you install your packages and add the --save arg to an npm install command it automatically appends it to the dependencies section or your package.json, which is convenient.
Solution 2 - node.js
Try pnpm instead of npm.
> pnpm uses hard links and symlinks to save one version of a module only ever once on a disk.
If you have npm installed, you can install in your terminal with:
npm install -g pnpm
To update your existing installations (and sub-directories) use:
pnpm recursive install
Or use the shorthand command (leave off -r if you need to target only one directory)
pnpm -r i
One helpful note: You may find some rare packages don't have all their dependencies defined. They might rely on the flat node_modules file directory structure of npm or yarn installs. If you run into issues of missing dependencies, use this command to hoist all the sub dependencies into a flat-file structure:
pnpm install --shamefully-hoist
It's best to avoid using the --shamefully-hoist flag as it defeats the purpose of using pnpm in the first place, so try using the command pnpm i your-missing-package first (See pnpm FAQ).
Solution 3 - node.js
I found a trick, just take a look at the Symbolic Links (symlinks) on Windows or Linux, it is working just like shortcuts but more powerful.
Simply you need to make a Junction for your node_modules folder anywhere you want. The junction is nothing but a short cut to your original node_modules folder. Create it inside your project folder where the actual node_modules would have been created if used npm install.
To achieve this you need at least one node_modules real folder then make a Junction to it in the other projects.
On Windows, you can either use the Command Prompt, or use an application. Using the Command Prompt gives you a bit more control, using an application is easier I suggest Link Shell Extension.
Solution 4 - node.js
Main directory should look like this
node_modules
Project 1
Project 2
Project 3
Project 4
just open the file Project 1/.angular-cli.json
change the schema
"$schema": "./node_modules/@angular/cli/lib/config/schema.json",
to
"$schema": "./../node_modules/@angular/cli/lib/config/schema.json"
and don't forget to create node_modules empty folder inside your project directory
Solution 5 - node.js
See also npm v7.0.0's support for workspaces
RFC https://github.com/npm/rfcs/blob/latest/implemented/0026-workspaces.md
Documentation https://docs.npmjs.com/cli/v7/using-npm/workspaces
Solution 6 - node.js
By looking at some articles it seems that Lerna
is a good tool for managing multiple projects inside a single directory (monorepo). It supports modules sharing without duplicating the entire packages in every folder and commands to install them in multiple projects.
pnpm is also a simple and efficient tool, which doesn't duplicate those modules which are already installed for other projects.
Solution 7 - node.js
Let's assume that having a single node_modules it should contain all the packages for all applications. thus your apps will also share most of the unique package.json entries (just the name should change)
my idea would be to have a single root and multiple src level as below
root\package.json
root\node_modules
root\\..
root\app1\src\\..
root\app2\src\\..
the only issue you might face would be having a backup of json (or tsconfig) for any app and restore them when you work on it or setup your startup scripts to serve any app