]
07-21-2023, 02:02 PM
Best solution would be [this][1] which is provided by npm documentation.
----------
For Ubuntu suggested solution is [Option#2][2]
Brief steps:
Make a directory for global installations:
**`mkdir ~/.npm-global`**
Configure npm to use the new directory path:
**`npm config set prefix '~/.npm-global'`**
`npm config get prefix` can help you to verify if prefix was updated or not. The result would be <Your Home Directory>/.npm-global
Open or create a ~/.profile file and add this line:
**`export PATH=~/.npm-global/bin:$PATH`**
Back on the command line, update your system variables:
**`source ~/.profile`**
Instead of steps 2-4 you can also use the corresponding ENV variable
(e.g. if you don't want to modify ~/.profile):
`NPM_CONFIG_PREFIX=~/.npm-global`
----------
For Mac suggested solution is [Option#3][3]
On Mac OS you can avoid this problem altogether by using the Homebrew package manager
**`brew install node`**
[1]:
----------
For Ubuntu suggested solution is [Option#2][2]
Brief steps:
Make a directory for global installations:
**`mkdir ~/.npm-global`**
Configure npm to use the new directory path:
**`npm config set prefix '~/.npm-global'`**
`npm config get prefix` can help you to verify if prefix was updated or not. The result would be <Your Home Directory>/.npm-global
Open or create a ~/.profile file and add this line:
**`export PATH=~/.npm-global/bin:$PATH`**
Back on the command line, update your system variables:
**`source ~/.profile`**
Instead of steps 2-4 you can also use the corresponding ENV variable
(e.g. if you don't want to modify ~/.profile):
`NPM_CONFIG_PREFIX=~/.npm-global`
----------
For Mac suggested solution is [Option#3][3]
On Mac OS you can avoid this problem altogether by using the Homebrew package manager
**`brew install node`**
[1]:
[To see links please register here]
[2]:[To see links please register here]
[3]:[To see links please register here]