react-script problem while having a node_module folder in the parent directory
I have another node_module folder in the parent folder of my project. I updated react-script to v2 and while I am trying to start the project I get an error like below:
The react-scripts package provided by Create React App requires a dependency:
"webpack": "4.19.1"
Don't try to install it manually: your package manager does it automatically.
However, a different version of webpack was detected higher up in the tree:
/parent_dir/node_modules/webpack (version: 4.20.2)
However, my project is in this directory and has its own node_module folder:
/parent_dir/my_project/node_modules/webpack (version: 4.20.2)
Everything goes OK if I delete parent's node_modules!
reactjs node-modules create-react-app react-scripts
add a comment |
I have another node_module folder in the parent folder of my project. I updated react-script to v2 and while I am trying to start the project I get an error like below:
The react-scripts package provided by Create React App requires a dependency:
"webpack": "4.19.1"
Don't try to install it manually: your package manager does it automatically.
However, a different version of webpack was detected higher up in the tree:
/parent_dir/node_modules/webpack (version: 4.20.2)
However, my project is in this directory and has its own node_module folder:
/parent_dir/my_project/node_modules/webpack (version: 4.20.2)
Everything goes OK if I delete parent's node_modules!
reactjs node-modules create-react-app react-scripts
add a comment |
I have another node_module folder in the parent folder of my project. I updated react-script to v2 and while I am trying to start the project I get an error like below:
The react-scripts package provided by Create React App requires a dependency:
"webpack": "4.19.1"
Don't try to install it manually: your package manager does it automatically.
However, a different version of webpack was detected higher up in the tree:
/parent_dir/node_modules/webpack (version: 4.20.2)
However, my project is in this directory and has its own node_module folder:
/parent_dir/my_project/node_modules/webpack (version: 4.20.2)
Everything goes OK if I delete parent's node_modules!
reactjs node-modules create-react-app react-scripts
I have another node_module folder in the parent folder of my project. I updated react-script to v2 and while I am trying to start the project I get an error like below:
The react-scripts package provided by Create React App requires a dependency:
"webpack": "4.19.1"
Don't try to install it manually: your package manager does it automatically.
However, a different version of webpack was detected higher up in the tree:
/parent_dir/node_modules/webpack (version: 4.20.2)
However, my project is in this directory and has its own node_module folder:
/parent_dir/my_project/node_modules/webpack (version: 4.20.2)
Everything goes OK if I delete parent's node_modules!
reactjs node-modules create-react-app react-scripts
reactjs node-modules create-react-app react-scripts
asked Nov 13 '18 at 13:45
Hadi RanjbarHadi Ranjbar
403413
403413
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I got that This is intended. We can skip preflight checks using instructions provided at the documentation in the react-scripts repo to solve the problem. However, I still don't know what is the reason for this pre-flight check.
1
agreed, I don't understand why webpack being in a parent folder matters to react-scripts
– Ben Clayton
Dec 11 '18 at 16:50
@BenClayton from Dan Abramov: We often had bug reports where npm produced bad installs (eg when mixed with yarn) and that caused plugins to find wrong webpack and fail with VERY confusing errors.
– Hadi Ranjbar
Dec 13 '18 at 20:21
add a comment |
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%2f53282430%2freact-script-problem-while-having-a-node-module-folder-in-the-parent-directory%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
I got that This is intended. We can skip preflight checks using instructions provided at the documentation in the react-scripts repo to solve the problem. However, I still don't know what is the reason for this pre-flight check.
1
agreed, I don't understand why webpack being in a parent folder matters to react-scripts
– Ben Clayton
Dec 11 '18 at 16:50
@BenClayton from Dan Abramov: We often had bug reports where npm produced bad installs (eg when mixed with yarn) and that caused plugins to find wrong webpack and fail with VERY confusing errors.
– Hadi Ranjbar
Dec 13 '18 at 20:21
add a comment |
I got that This is intended. We can skip preflight checks using instructions provided at the documentation in the react-scripts repo to solve the problem. However, I still don't know what is the reason for this pre-flight check.
1
agreed, I don't understand why webpack being in a parent folder matters to react-scripts
– Ben Clayton
Dec 11 '18 at 16:50
@BenClayton from Dan Abramov: We often had bug reports where npm produced bad installs (eg when mixed with yarn) and that caused plugins to find wrong webpack and fail with VERY confusing errors.
– Hadi Ranjbar
Dec 13 '18 at 20:21
add a comment |
I got that This is intended. We can skip preflight checks using instructions provided at the documentation in the react-scripts repo to solve the problem. However, I still don't know what is the reason for this pre-flight check.
I got that This is intended. We can skip preflight checks using instructions provided at the documentation in the react-scripts repo to solve the problem. However, I still don't know what is the reason for this pre-flight check.
answered Nov 19 '18 at 8:48
Hadi RanjbarHadi Ranjbar
403413
403413
1
agreed, I don't understand why webpack being in a parent folder matters to react-scripts
– Ben Clayton
Dec 11 '18 at 16:50
@BenClayton from Dan Abramov: We often had bug reports where npm produced bad installs (eg when mixed with yarn) and that caused plugins to find wrong webpack and fail with VERY confusing errors.
– Hadi Ranjbar
Dec 13 '18 at 20:21
add a comment |
1
agreed, I don't understand why webpack being in a parent folder matters to react-scripts
– Ben Clayton
Dec 11 '18 at 16:50
@BenClayton from Dan Abramov: We often had bug reports where npm produced bad installs (eg when mixed with yarn) and that caused plugins to find wrong webpack and fail with VERY confusing errors.
– Hadi Ranjbar
Dec 13 '18 at 20:21
1
1
agreed, I don't understand why webpack being in a parent folder matters to react-scripts
– Ben Clayton
Dec 11 '18 at 16:50
agreed, I don't understand why webpack being in a parent folder matters to react-scripts
– Ben Clayton
Dec 11 '18 at 16:50
@BenClayton from Dan Abramov: We often had bug reports where npm produced bad installs (eg when mixed with yarn) and that caused plugins to find wrong webpack and fail with VERY confusing errors.
– Hadi Ranjbar
Dec 13 '18 at 20:21
@BenClayton from Dan Abramov: We often had bug reports where npm produced bad installs (eg when mixed with yarn) and that caused plugins to find wrong webpack and fail with VERY confusing errors.
– Hadi Ranjbar
Dec 13 '18 at 20:21
add a comment |
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%2f53282430%2freact-script-problem-while-having-a-node-module-folder-in-the-parent-directory%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