@Angular in global and non-local repository for all projects

Question

I installed @angular/cli like this:

npm install -g @angular/cli

I created a project like this:

ng new name-project

So far so good, but there is the possibility that when you create a project with eating ng new it does not copy the @Angula folder to location, but it uses the one from the global repository?

Reason for the question:

A clean design with only the angular has approximately 28,000 files with the total size of approximately 200 MB, to backup takes a lot, out it consumes hard disk space. I would like to unify the packages that are possible in the global repository and whenever I create my projects they will access the libraries there because all the projects will have the same versions of the libraries and if I update one all the projects will be updated.

===========================================================================

I ran the following lines on CMD simulating a project from scratch.

I created a folder Projects and inside it I made the commands:

mkdir node_modules
echo {} >> package.json
npm i @angular/cli --save
ng new projeto1 --skip-install

at the end presented the following message when I used ng new project1

"You cannot use the new command Inside an Angular CLI project."

Answer 1

Yes, you can create a directory node_modules among projects.

Of node.js documentation

If the module Identifier passed to require() is not a core module, and does not Begin with '/', '../', or './', then Node.js Starts at the Parent directory of the Current module, and adds /node_modules, and Attempts to load the module from that Location. Node will not append node_modules to a path already ending in node_modules.

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.js 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 basically what you should do is create a directory called node_modules at the root of your project directory, saving in this directory the common modules between your projects:

meus-projetos
│   package.json    
│
└───node_modules
│   │
│   └───@angular
│       │   ...
│   
└───meu-projeto-angular-01
│   │   tsconfig.json
│   │   ...
│   │
└───meu-projeto-angular-02
│   │   tsconfig.json
│   │   ...

Notice how there is only one file package.json that manages the shared directory node_modules.

Incidentally, using the command

npm install <nome-do-pacote> --save

will ensure automatic update of the dependencies section of that file.