NPM installing global packages in /root/node_modules
I've installed and used node/npm on more systems than I care to count, the majority being Linux/CentOS machines. I have a CentOS 7 installation that installs global packages in /root/node_modules. Thus, they won't be globally available. npm root also confirms this. Of course, I could probably use prefix, or any similar NVM-ish hack; but I'd rather not.
I also tried installing as devDependencies. One side effect was that pm2 cluster module was not spawning processes on all my cores, as I've seen on my other CentOS development server.
Please help me out. I've repeatedly uninstalled, purged and reinstalled node, npm and yarn.
centos node.js
asked Jan 11 at 19:48
iMykeiMyke
13
add a comment |
I've installed and used node/npm on more systems than I care to count, the majority being Linux/CentOS machines. I have a CentOS 7 installation that installs global packages in /root/node_modules. Thus, they won't be globally available. npm root also confirms this. Of course, I could probably use prefix, or any similar NVM-ish hack; but I'd rather not.
I also tried installing as devDependencies. One side effect was that pm2 cluster module was not spawning processes on all my cores, as I've seen on my other CentOS development server.
Please help me out. I've repeatedly uninstalled, purged and reinstalled node, npm and yarn.
centos node.js
asked Jan 11 at 19:48
iMykeiMyke
13
add a comment |
I've installed and used node/npm on more systems than I care to count, the majority being Linux/CentOS machines. I have a CentOS 7 installation that installs global packages in /root/node_modules. Thus, they won't be globally available. npm root also confirms this. Of course, I could probably use prefix, or any similar NVM-ish hack; but I'd rather not.
I also tried installing as devDependencies. One side effect was that pm2 cluster module was not spawning processes on all my cores, as I've seen on my other CentOS development server.
Please help me out. I've repeatedly uninstalled, purged and reinstalled node, npm and yarn.
centos node.js
asked Jan 11 at 19:48
iMykeiMyke
13
I've installed and used node/npm on more systems than I care to count, the majority being Linux/CentOS machines. I have a CentOS 7 installation that installs global packages in /root/node_modules. Thus, they won't be globally available. npm root also confirms this. Of course, I could probably use prefix, or any similar NVM-ish hack; but I'd rather not.
I also tried installing as devDependencies. One side effect was that pm2 cluster module was not spawning processes on all my cores, as I've seen on my other CentOS development server.
Please help me out. I've repeatedly uninstalled, purged and reinstalled node, npm and yarn.
centos node.js
centos node.js
asked Jan 11 at 19:48
iMykeiMyke
13
asked Jan 11 at 19:48
iMykeiMyke
13
asked Jan 11 at 19:48
iMykeiMyke
13
asked Jan 11 at 19:48
iMykeiMyke
13
asked Jan 11 at 19:48
iMykeiMyke
13
13
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
According to this answer to an identical question on StackOverflow,
In case you want to have local packages at a globally available path, you could install to your filesystem root. cd / and from there npm install .. all users would have read access to that folder by default. Node will find those packages.
I hope this helps someone else!
answered Jan 19 at 16:44
iMykeiMyke
13
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393305%2fnpm-installing-global-packages-in-root-node-modules%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
According to this answer to an identical question on StackOverflow,
In case you want to have local packages at a globally available path, you could install to your filesystem root. cd / and from there npm install .. all users would have read access to that folder by default. Node will find those packages.
I hope this helps someone else!
answered Jan 19 at 16:44
iMykeiMyke
13
add a comment |
According to this answer to an identical question on StackOverflow,
In case you want to have local packages at a globally available path, you could install to your filesystem root. cd / and from there npm install .. all users would have read access to that folder by default. Node will find those packages.
I hope this helps someone else!
answered Jan 19 at 16:44
iMykeiMyke
13
add a comment |
According to this answer to an identical question on StackOverflow,
In case you want to have local packages at a globally available path, you could install to your filesystem root. cd / and from there npm install .. all users would have read access to that folder by default. Node will find those packages.
I hope this helps someone else!
answered Jan 19 at 16:44
iMykeiMyke
13
According to this answer to an identical question on StackOverflow,
In case you want to have local packages at a globally available path, you could install to your filesystem root. cd / and from there npm install .. all users would have read access to that folder by default. Node will find those packages.
I hope this helps someone else!
answered Jan 19 at 16:44
iMykeiMyke
13
answered Jan 19 at 16:44
iMykeiMyke
13
answered Jan 19 at 16:44
iMykeiMyke
13
answered Jan 19 at 16:44
iMykeiMyke
13
13
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393305%2fnpm-installing-global-packages-in-root-node-modules%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
