nodejs install through anaconda causing cross machine compatibility issues on linux
This problem may be hard to reproducibly describe but hopefully this works. I'm using two different machines (laptop and desktop), and following the steps below on both.
I am creating a conda environment like this:
conda create --name webdev --no-default-packages
Then I am only installing nodejs at the moment, like this:
conda install -c conda-forge nodejs
The resulting environment has only three things in it:
# Name Version Build Channel
libgcc-ng 7.2.0 hdf63c60_3 conda-forge
libstdcxx-ng 7.2.0 hdf63c60_3 conda-forge
nodejs 10.8.0 hfc679d8_1 conda-forge
Just to illustrate, I can then create a new react project like this:
create-react-app my-app
cd my-app
npm start
And the web server starts just fine and everything functions as expected. The problem I then have is that if I use my laptop to navigate into the project folder I created on my desktop and try npm start
(or vice versa) I get the following error:
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module '../scripts/start'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.resolve (internal/modules/cjs/helpers.js:30:19)
at Object.<anonymous> (/home/me/my-app/node_modules/.bin/react-scripts:35:25)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:266:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@0.1.0 start 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/me/.npm/_logs/2018-11-21T01_24_45_031Z-debug.log
Strangely enough I can export the conda environment I created on my desktop, use it to create a new environment on my laptop, and will still get the error when I try to run the project I created on my desktop (and vice versa).
node.js
add a comment |
This problem may be hard to reproducibly describe but hopefully this works. I'm using two different machines (laptop and desktop), and following the steps below on both.
I am creating a conda environment like this:
conda create --name webdev --no-default-packages
Then I am only installing nodejs at the moment, like this:
conda install -c conda-forge nodejs
The resulting environment has only three things in it:
# Name Version Build Channel
libgcc-ng 7.2.0 hdf63c60_3 conda-forge
libstdcxx-ng 7.2.0 hdf63c60_3 conda-forge
nodejs 10.8.0 hfc679d8_1 conda-forge
Just to illustrate, I can then create a new react project like this:
create-react-app my-app
cd my-app
npm start
And the web server starts just fine and everything functions as expected. The problem I then have is that if I use my laptop to navigate into the project folder I created on my desktop and try npm start
(or vice versa) I get the following error:
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module '../scripts/start'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.resolve (internal/modules/cjs/helpers.js:30:19)
at Object.<anonymous> (/home/me/my-app/node_modules/.bin/react-scripts:35:25)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:266:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@0.1.0 start 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/me/.npm/_logs/2018-11-21T01_24_45_031Z-debug.log
Strangely enough I can export the conda environment I created on my desktop, use it to create a new environment on my laptop, and will still get the error when I try to run the project I created on my desktop (and vice versa).
node.js
add a comment |
This problem may be hard to reproducibly describe but hopefully this works. I'm using two different machines (laptop and desktop), and following the steps below on both.
I am creating a conda environment like this:
conda create --name webdev --no-default-packages
Then I am only installing nodejs at the moment, like this:
conda install -c conda-forge nodejs
The resulting environment has only three things in it:
# Name Version Build Channel
libgcc-ng 7.2.0 hdf63c60_3 conda-forge
libstdcxx-ng 7.2.0 hdf63c60_3 conda-forge
nodejs 10.8.0 hfc679d8_1 conda-forge
Just to illustrate, I can then create a new react project like this:
create-react-app my-app
cd my-app
npm start
And the web server starts just fine and everything functions as expected. The problem I then have is that if I use my laptop to navigate into the project folder I created on my desktop and try npm start
(or vice versa) I get the following error:
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module '../scripts/start'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.resolve (internal/modules/cjs/helpers.js:30:19)
at Object.<anonymous> (/home/me/my-app/node_modules/.bin/react-scripts:35:25)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:266:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@0.1.0 start 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/me/.npm/_logs/2018-11-21T01_24_45_031Z-debug.log
Strangely enough I can export the conda environment I created on my desktop, use it to create a new environment on my laptop, and will still get the error when I try to run the project I created on my desktop (and vice versa).
node.js
This problem may be hard to reproducibly describe but hopefully this works. I'm using two different machines (laptop and desktop), and following the steps below on both.
I am creating a conda environment like this:
conda create --name webdev --no-default-packages
Then I am only installing nodejs at the moment, like this:
conda install -c conda-forge nodejs
The resulting environment has only three things in it:
# Name Version Build Channel
libgcc-ng 7.2.0 hdf63c60_3 conda-forge
libstdcxx-ng 7.2.0 hdf63c60_3 conda-forge
nodejs 10.8.0 hfc679d8_1 conda-forge
Just to illustrate, I can then create a new react project like this:
create-react-app my-app
cd my-app
npm start
And the web server starts just fine and everything functions as expected. The problem I then have is that if I use my laptop to navigate into the project folder I created on my desktop and try npm start
(or vice versa) I get the following error:
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module '../scripts/start'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.resolve (internal/modules/cjs/helpers.js:30:19)
at Object.<anonymous> (/home/me/my-app/node_modules/.bin/react-scripts:35:25)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:266:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@0.1.0 start 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/me/.npm/_logs/2018-11-21T01_24_45_031Z-debug.log
Strangely enough I can export the conda environment I created on my desktop, use it to create a new environment on my laptop, and will still get the error when I try to run the project I created on my desktop (and vice versa).
node.js
node.js
asked Nov 21 at 1:30
The Nightman
2,04861634
2,04861634
add a comment |
add a comment |
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%2f53404070%2fnodejs-install-through-anaconda-causing-cross-machine-compatibility-issues-on-li%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53404070%2fnodejs-install-through-anaconda-causing-cross-machine-compatibility-issues-on-li%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