Mixing
Child module is unable to install dependencies (global install) - Relative path issue?
I have an npm package with a structure like this:
./
./backend
./package.json
package.json
So basically two npm modules in the same folder, one being a child of the other, file structure wise.
The way I install is, is that I put a post-install script in the parent package.json:
"postinstall": "cd backend && npm install && cd .."
What happens ONLY if I install it globally: It first prints some warnings that basically the packages weren't installed. Like this:
npm WARN enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/trim-newlines/package.json'
Those appear for all dependencies in ./backend/package.json.
I already run the installation with the --unsafe-perm flag:
npm install -g inschpektor --unsafe-perm which installs the parent package.json, that contains the postinstall script.
The final log error message I get is this one:
npm ERR! path /usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_46_911Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! inschpektor@0.9.1 postinstall: `cd backend && npm install && cd ..`
npm ERR! Exit status 254
npm ERR!
npm ERR! Failed at the inschpektor@0.9.1 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_47_511Z-debug.log
What am I doing wrong? Or do you maybe see flaws in the way I'm setting things up?
Here is the link to get git repo, if you would like to further analyze it: https://github.com/codepleb/inschpektor
node.js npm npm-install node-modules npm-scripts
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
add a comment |
I have an npm package with a structure like this:
./
./backend
./package.json
package.json
So basically two npm modules in the same folder, one being a child of the other, file structure wise.
The way I install is, is that I put a post-install script in the parent package.json:
"postinstall": "cd backend && npm install && cd .."
What happens ONLY if I install it globally: It first prints some warnings that basically the packages weren't installed. Like this:
npm WARN enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/trim-newlines/package.json'
Those appear for all dependencies in ./backend/package.json.
I already run the installation with the --unsafe-perm flag:
npm install -g inschpektor --unsafe-perm which installs the parent package.json, that contains the postinstall script.
The final log error message I get is this one:
npm ERR! path /usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_46_911Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! inschpektor@0.9.1 postinstall: `cd backend && npm install && cd ..`
npm ERR! Exit status 254
npm ERR!
npm ERR! Failed at the inschpektor@0.9.1 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_47_511Z-debug.log
What am I doing wrong? Or do you maybe see flaws in the way I'm setting things up?
Here is the link to get git repo, if you would like to further analyze it: https://github.com/codepleb/inschpektor
node.js npm npm-install node-modules npm-scripts
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
From what I can tell, runningnpm installon the project root of your app works without a problem, and thebackenddirectory doesn't even contain apackage.jsonfile. Is this still relevant?
– Itai Steinherz
Jan 15 at 22:12
@ItaiSteinherz I moved everthing in the parent node_modules folder instead of having 2 npm projects in one. Now, all the files of the "submodule" are linking to the dependencies of the main node_modules. Not sure which is the better approach. If you would find a better solution, feel free to post. This was basically the state of when I was asking this question (git hash): a907bf8dd845d63a3fc1b30dea27bc2641936639
– codepleb
Jan 16 at 13:19
npm installseems to work fine for me on the revision you mentioned. Can you mention the exact commands used to reproduce?
– Itai Steinherz
Jan 16 at 22:09
Why won't you makebackenda separate package, so it could be included into your main package as a dependency?
– Leonid Beschastny
Jan 17 at 20:29
@ItaiSteinherz You need to globally install it. The problem was on linux for me. Not all the time, or it only worked initially. I can't quantify it tbh.
– codepleb
Jan 20 at 16:26
add a comment |
I have an npm package with a structure like this:
./
./backend
./package.json
package.json
So basically two npm modules in the same folder, one being a child of the other, file structure wise.
The way I install is, is that I put a post-install script in the parent package.json:
"postinstall": "cd backend && npm install && cd .."
What happens ONLY if I install it globally: It first prints some warnings that basically the packages weren't installed. Like this:
npm WARN enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/trim-newlines/package.json'
Those appear for all dependencies in ./backend/package.json.
I already run the installation with the --unsafe-perm flag:
npm install -g inschpektor --unsafe-perm which installs the parent package.json, that contains the postinstall script.
The final log error message I get is this one:
npm ERR! path /usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_46_911Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! inschpektor@0.9.1 postinstall: `cd backend && npm install && cd ..`
npm ERR! Exit status 254
npm ERR!
npm ERR! Failed at the inschpektor@0.9.1 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_47_511Z-debug.log
What am I doing wrong? Or do you maybe see flaws in the way I'm setting things up?
Here is the link to get git repo, if you would like to further analyze it: https://github.com/codepleb/inschpektor
node.js npm npm-install node-modules npm-scripts
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
I have an npm package with a structure like this:
./
./backend
./package.json
package.json
So basically two npm modules in the same folder, one being a child of the other, file structure wise.
The way I install is, is that I put a post-install script in the parent package.json:
"postinstall": "cd backend && npm install && cd .."
What happens ONLY if I install it globally: It first prints some warnings that basically the packages weren't installed. Like this:
npm WARN enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/trim-newlines/package.json'
Those appear for all dependencies in ./backend/package.json.
I already run the installation with the --unsafe-perm flag:
npm install -g inschpektor --unsafe-perm which installs the parent package.json, that contains the postinstall script.
The final log error message I get is this one:
npm ERR! path /usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/usr/lib/node_modules/inschpektor/backend/node_modules/ansi-regex/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_46_911Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! inschpektor@0.9.1 postinstall: `cd backend && npm install && cd ..`
npm ERR! Exit status 254
npm ERR!
npm ERR! Failed at the inschpektor@0.9.1 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/codepleb/.npm/_logs/2019-01-02T01_52_47_511Z-debug.log
What am I doing wrong? Or do you maybe see flaws in the way I'm setting things up?
Here is the link to get git repo, if you would like to further analyze it: https://github.com/codepleb/inschpektor
node.js npm npm-install node-modules npm-scripts
node.js npm npm-install node-modules npm-scripts
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
asked Jan 2 at 12:16
codeplebcodepleb
3,63263863
3,63263863
From what I can tell, runningnpm installon the project root of your app works without a problem, and thebackenddirectory doesn't even contain apackage.jsonfile. Is this still relevant?
– Itai Steinherz
Jan 15 at 22:12
@ItaiSteinherz I moved everthing in the parent node_modules folder instead of having 2 npm projects in one. Now, all the files of the "submodule" are linking to the dependencies of the main node_modules. Not sure which is the better approach. If you would find a better solution, feel free to post. This was basically the state of when I was asking this question (git hash): a907bf8dd845d63a3fc1b30dea27bc2641936639
– codepleb
Jan 16 at 13:19
npm installseems to work fine for me on the revision you mentioned. Can you mention the exact commands used to reproduce?
– Itai Steinherz
Jan 16 at 22:09
Why won't you makebackenda separate package, so it could be included into your main package as a dependency?
– Leonid Beschastny
Jan 17 at 20:29
@ItaiSteinherz You need to globally install it. The problem was on linux for me. Not all the time, or it only worked initially. I can't quantify it tbh.
– codepleb
Jan 20 at 16:26
add a comment |
From what I can tell, runningnpm installon the project root of your app works without a problem, and thebackenddirectory doesn't even contain apackage.jsonfile. Is this still relevant?
– Itai Steinherz
Jan 15 at 22:12
@ItaiSteinherz I moved everthing in the parent node_modules folder instead of having 2 npm projects in one. Now, all the files of the "submodule" are linking to the dependencies of the main node_modules. Not sure which is the better approach. If you would find a better solution, feel free to post. This was basically the state of when I was asking this question (git hash): a907bf8dd845d63a3fc1b30dea27bc2641936639
– codepleb
Jan 16 at 13:19
npm installseems to work fine for me on the revision you mentioned. Can you mention the exact commands used to reproduce?
– Itai Steinherz
Jan 16 at 22:09
Why won't you makebackenda separate package, so it could be included into your main package as a dependency?
– Leonid Beschastny
Jan 17 at 20:29
@ItaiSteinherz You need to globally install it. The problem was on linux for me. Not all the time, or it only worked initially. I can't quantify it tbh.
– codepleb
Jan 20 at 16:26
From what I can tell, running
npm install on the project root of your app works without a problem, and the backend directory doesn't even contain a package.json file. Is this still relevant?– Itai Steinherz
Jan 15 at 22:12
From what I can tell, running
npm install on the project root of your app works without a problem, and the backend directory doesn't even contain a package.json file. Is this still relevant?– Itai Steinherz
Jan 15 at 22:12
@ItaiSteinherz I moved everthing in the parent node_modules folder instead of having 2 npm projects in one. Now, all the files of the "submodule" are linking to the dependencies of the main node_modules. Not sure which is the better approach. If you would find a better solution, feel free to post. This was basically the state of when I was asking this question (git hash): a907bf8dd845d63a3fc1b30dea27bc2641936639
– codepleb
Jan 16 at 13:19
@ItaiSteinherz I moved everthing in the parent node_modules folder instead of having 2 npm projects in one. Now, all the files of the "submodule" are linking to the dependencies of the main node_modules. Not sure which is the better approach. If you would find a better solution, feel free to post. This was basically the state of when I was asking this question (git hash): a907bf8dd845d63a3fc1b30dea27bc2641936639
– codepleb
Jan 16 at 13:19
npm install seems to work fine for me on the revision you mentioned. Can you mention the exact commands used to reproduce?– Itai Steinherz
Jan 16 at 22:09
npm install seems to work fine for me on the revision you mentioned. Can you mention the exact commands used to reproduce?– Itai Steinherz
Jan 16 at 22:09
Why won't you make
backend a separate package, so it could be included into your main package as a dependency?– Leonid Beschastny
Jan 17 at 20:29
Why won't you make
backend a separate package, so it could be included into your main package as a dependency?– Leonid Beschastny
Jan 17 at 20:29
@ItaiSteinherz You need to globally install it. The problem was on linux for me. Not all the time, or it only worked initially. I can't quantify it tbh.
– codepleb
Jan 20 at 16:26
@ItaiSteinherz You need to globally install it. The problem was on linux for me. Not all the time, or it only worked initially. I can't quantify it tbh.
– codepleb
Jan 20 at 16:26
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f54006219%2fchild-module-is-unable-to-install-dependencies-global-install-relative-path%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f54006219%2fchild-module-is-unable-to-install-dependencies-global-install-relative-path%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
From what I can tell, running
npm installon the project root of your app works without a problem, and thebackenddirectory doesn't even contain apackage.jsonfile. Is this still relevant?– Itai Steinherz
Jan 15 at 22:12
@ItaiSteinherz I moved everthing in the parent node_modules folder instead of having 2 npm projects in one. Now, all the files of the "submodule" are linking to the dependencies of the main node_modules. Not sure which is the better approach. If you would find a better solution, feel free to post. This was basically the state of when I was asking this question (git hash): a907bf8dd845d63a3fc1b30dea27bc2641936639
– codepleb
Jan 16 at 13:19
npm installseems to work fine for me on the revision you mentioned. Can you mention the exact commands used to reproduce?– Itai Steinherz
Jan 16 at 22:09
Why won't you make
backenda separate package, so it could be included into your main package as a dependency?– Leonid Beschastny
Jan 17 at 20:29
@ItaiSteinherz You need to globally install it. The problem was on linux for me. Not all the time, or it only worked initially. I can't quantify it tbh.
– codepleb
Jan 20 at 16:26