Mixing
eslint error on deployment on local server of react web app
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
D:chintublog-exambunker-masterblog-exambunker-masternode_moduleseslint (version: 5.6.1)
how to install the version 5.6.0 I am installing the eslint it always gets installed with the latest version, can someone suggest me what to do?
reactjs
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
add a comment |
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
D:chintublog-exambunker-masterblog-exambunker-masternode_moduleseslint (version: 5.6.1)
how to install the version 5.6.0 I am installing the eslint it always gets installed with the latest version, can someone suggest me what to do?
reactjs
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
add a comment |
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
D:chintublog-exambunker-masterblog-exambunker-masternode_moduleseslint (version: 5.6.1)
how to install the version 5.6.0 I am installing the eslint it always gets installed with the latest version, can someone suggest me what to do?
reactjs
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
D:chintublog-exambunker-masterblog-exambunker-masternode_moduleseslint (version: 5.6.1)
how to install the version 5.6.0 I am installing the eslint it always gets installed with the latest version, can someone suggest me what to do?
reactjs
reactjs
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
edited Oct 28 '18 at 18:45
Azat Ibrakov
4,26871631
4,26871631
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
asked Oct 1 '18 at 7:44
abhinav pandeyabhinav pandey
2613
2613
add a comment |
add a comment |
11 Answers
11
active
oldest
votes
I have the exactly same problem. I have tried everithing from those Suggestions:
1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
2. Delete node_modules in your project folder.
3. Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
4. Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if C:UsersUsernode_moduleseslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
nothing worked. every time I am doing "npm install"/"yarn" it keeps install the old version of eslint.
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
Me too couldn't find a solution for this
– abhinav pandey
Oct 5 '18 at 11:03
add a comment |
ok I find my issue: I had npm packeges and some more crap outside the projects folders (on c:/users/user) they may had the old version of eslint. cheack it out and tell me if you still have the problem or not.
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
add a comment |
I searched where the eslint was with:
npm ls eslint
then I deleted it with:
npm uninstall ls eslint
Finally I ran
npm start
and it worked.
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
answered Oct 28 '18 at 18:37
MileMile
91
1
this doesn't explain the root of the issue that OP is struggling with, reinstalling every time doesn't look like a solution but a workaround
– Azat Ibrakov
Oct 28 '18 at 18:47
add a comment |
(Do not do what I did if you don't read everthing I posted) At least with me, I just downgraded my eslint 5.8.0 to 5.6.0 (manually). Why? Because when I use some eslint library like airbnb, it installs the latest version of eslint (5.8.0) automatically, the problem here is that this version has conflict with the previous eslint version used by react (5.6.0), so when you downgrade, you just return to the previous eslint installed, so it's working fine here, but you've to be careful when you update your react version.
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
add a comment |
The error is an incompatibility between eslint and babel-eslint versions. To do solve this, firstly you need to remove your eslint package using npm uninstall eslint. This command will delete your eslint package. After this, you need to install the 5.6.0 version of eslint, so write this command npm i eslint@5.6.0. I hope that this will be helpful for you. Also, you can delete your node_modules folder and then install it.
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
add a comment |
What solved this for me, was that in the error message, it told me that there was eslint installed in project with 5.6.0 and another installed in users/andrew/nodemodules/eslint with a version of 4.1.6 I tried doing a npm uninstall -g eslint but that didnt work so then I just searched for all the files and folders within users/andrew/nodemodules/eslint
and deleted them, and it worked for then.
I'm not sure if this is a good way to do it, but its worked.
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
add a comment |
Create a file .env in your root directory.
And you can ignore the check by putting
SKIP_PREFLIGHT_CHECK=true
in .env file.
Ref: https://github.com/facebook/create-react-app/issues/5247#issuecomment-427221678
Edit: This is not the solution to this problem. It is just to ignore the error as it is discussed in the issue.
edited Feb 4 at 6:26
Vipul Rawat
184
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
add a comment |
Simple delete package-lock.json and node_modules then run npm install then
npm start
else you could install
npm i eslint@5.6.0 then
npm start
enjoy your work :)
- List item
answered Feb 22 at 18:23
ManasManas
605
add a comment |
I deleted a node modules folder that contained an older version of eslint. I found this to be the easiest solution rather than changing dependencies.
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
add a comment |
Add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
1
That does not solve the problem, it just hides the error message
– Treycos
Nov 7 '18 at 17:51
add a comment |
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
/Users/macbook/node_modules/eslint (version: 3.19.0)
Manually installing incompatible versions is known to cause hard-to-debug issues.
If prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.
To fix the dependency tree, try following the steps below in the exact order:
- Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
- Delete node_modules in your project folder.
- Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
- Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if /Users/macbook/node_modules/eslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.
P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
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! /Users/macbook/.npm/_logs/2018-11-01T15_26_42_405Z-debug.log
answered Nov 1 '18 at 15:29
BambaBamba
11
3
Congratulation, you copy-pasted the full error message, but this is not an answer
– Treycos
Nov 7 '18 at 17:52
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%2f52586594%2feslint-error-on-deployment-on-local-server-of-react-web-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
11 Answers
11
active
oldest
votes
11 Answers
11
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have the exactly same problem. I have tried everithing from those Suggestions:
1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
2. Delete node_modules in your project folder.
3. Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
4. Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if C:UsersUsernode_moduleseslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
nothing worked. every time I am doing "npm install"/"yarn" it keeps install the old version of eslint.
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
Me too couldn't find a solution for this
– abhinav pandey
Oct 5 '18 at 11:03
add a comment |
I have the exactly same problem. I have tried everithing from those Suggestions:
1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
2. Delete node_modules in your project folder.
3. Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
4. Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if C:UsersUsernode_moduleseslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
nothing worked. every time I am doing "npm install"/"yarn" it keeps install the old version of eslint.
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
Me too couldn't find a solution for this
– abhinav pandey
Oct 5 '18 at 11:03
add a comment |
I have the exactly same problem. I have tried everithing from those Suggestions:
1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
2. Delete node_modules in your project folder.
3. Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
4. Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if C:UsersUsernode_moduleseslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
nothing worked. every time I am doing "npm install"/"yarn" it keeps install the old version of eslint.
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
I have the exactly same problem. I have tried everithing from those Suggestions:
1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
2. Delete node_modules in your project folder.
3. Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
4. Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if C:UsersUsernode_moduleseslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
nothing worked. every time I am doing "npm install"/"yarn" it keeps install the old version of eslint.
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
answered Oct 5 '18 at 11:00
Noga-zNoga-z
11
11
Me too couldn't find a solution for this
– abhinav pandey
Oct 5 '18 at 11:03
add a comment |
Me too couldn't find a solution for this
– abhinav pandey
Oct 5 '18 at 11:03
Me too couldn't find a solution for this
– abhinav pandey
Oct 5 '18 at 11:03
Me too couldn't find a solution for this
– abhinav pandey
Oct 5 '18 at 11:03
add a comment |
ok I find my issue: I had npm packeges and some more crap outside the projects folders (on c:/users/user) they may had the old version of eslint. cheack it out and tell me if you still have the problem or not.
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
add a comment |
ok I find my issue: I had npm packeges and some more crap outside the projects folders (on c:/users/user) they may had the old version of eslint. cheack it out and tell me if you still have the problem or not.
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
add a comment |
ok I find my issue: I had npm packeges and some more crap outside the projects folders (on c:/users/user) they may had the old version of eslint. cheack it out and tell me if you still have the problem or not.
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
ok I find my issue: I had npm packeges and some more crap outside the projects folders (on c:/users/user) they may had the old version of eslint. cheack it out and tell me if you still have the problem or not.
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
answered Oct 5 '18 at 11:29
Noga-zNoga-z
11
11
add a comment |
add a comment |
I searched where the eslint was with:
npm ls eslint
then I deleted it with:
npm uninstall ls eslint
Finally I ran
npm start
and it worked.
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
answered Oct 28 '18 at 18:37
MileMile
91
1
this doesn't explain the root of the issue that OP is struggling with, reinstalling every time doesn't look like a solution but a workaround
– Azat Ibrakov
Oct 28 '18 at 18:47
add a comment |
I searched where the eslint was with:
npm ls eslint
then I deleted it with:
npm uninstall ls eslint
Finally I ran
npm start
and it worked.
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
answered Oct 28 '18 at 18:37
MileMile
91
1
this doesn't explain the root of the issue that OP is struggling with, reinstalling every time doesn't look like a solution but a workaround
– Azat Ibrakov
Oct 28 '18 at 18:47
add a comment |
I searched where the eslint was with:
npm ls eslint
then I deleted it with:
npm uninstall ls eslint
Finally I ran
npm start
and it worked.
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
answered Oct 28 '18 at 18:37
MileMile
91
I searched where the eslint was with:
npm ls eslint
then I deleted it with:
npm uninstall ls eslint
Finally I ran
npm start
and it worked.
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
answered Oct 28 '18 at 18:37
MileMile
91
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
edited Oct 28 '18 at 18:43
Azat Ibrakov
4,26871631
4,26871631
answered Oct 28 '18 at 18:37
MileMile
91
answered Oct 28 '18 at 18:37
MileMile
91
answered Oct 28 '18 at 18:37
MileMile
91
91
1
this doesn't explain the root of the issue that OP is struggling with, reinstalling every time doesn't look like a solution but a workaround
– Azat Ibrakov
Oct 28 '18 at 18:47
add a comment |
1
this doesn't explain the root of the issue that OP is struggling with, reinstalling every time doesn't look like a solution but a workaround
– Azat Ibrakov
Oct 28 '18 at 18:47
1
1
this doesn't explain the root of the issue that OP is struggling with, reinstalling every time doesn't look like a solution but a workaround
– Azat Ibrakov
Oct 28 '18 at 18:47
this doesn't explain the root of the issue that OP is struggling with, reinstalling every time doesn't look like a solution but a workaround
– Azat Ibrakov
Oct 28 '18 at 18:47
add a comment |
(Do not do what I did if you don't read everthing I posted) At least with me, I just downgraded my eslint 5.8.0 to 5.6.0 (manually). Why? Because when I use some eslint library like airbnb, it installs the latest version of eslint (5.8.0) automatically, the problem here is that this version has conflict with the previous eslint version used by react (5.6.0), so when you downgrade, you just return to the previous eslint installed, so it's working fine here, but you've to be careful when you update your react version.
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
add a comment |
(Do not do what I did if you don't read everthing I posted) At least with me, I just downgraded my eslint 5.8.0 to 5.6.0 (manually). Why? Because when I use some eslint library like airbnb, it installs the latest version of eslint (5.8.0) automatically, the problem here is that this version has conflict with the previous eslint version used by react (5.6.0), so when you downgrade, you just return to the previous eslint installed, so it's working fine here, but you've to be careful when you update your react version.
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
add a comment |
(Do not do what I did if you don't read everthing I posted) At least with me, I just downgraded my eslint 5.8.0 to 5.6.0 (manually). Why? Because when I use some eslint library like airbnb, it installs the latest version of eslint (5.8.0) automatically, the problem here is that this version has conflict with the previous eslint version used by react (5.6.0), so when you downgrade, you just return to the previous eslint installed, so it's working fine here, but you've to be careful when you update your react version.
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
(Do not do what I did if you don't read everthing I posted) At least with me, I just downgraded my eslint 5.8.0 to 5.6.0 (manually). Why? Because when I use some eslint library like airbnb, it installs the latest version of eslint (5.8.0) automatically, the problem here is that this version has conflict with the previous eslint version used by react (5.6.0), so when you downgrade, you just return to the previous eslint installed, so it's working fine here, but you've to be careful when you update your react version.
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
answered Nov 2 '18 at 17:09
Rodrigo FonsecaRodrigo Fonseca
614619
614619
add a comment |
add a comment |
The error is an incompatibility between eslint and babel-eslint versions. To do solve this, firstly you need to remove your eslint package using npm uninstall eslint. This command will delete your eslint package. After this, you need to install the 5.6.0 version of eslint, so write this command npm i eslint@5.6.0. I hope that this will be helpful for you. Also, you can delete your node_modules folder and then install it.
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
add a comment |
The error is an incompatibility between eslint and babel-eslint versions. To do solve this, firstly you need to remove your eslint package using npm uninstall eslint. This command will delete your eslint package. After this, you need to install the 5.6.0 version of eslint, so write this command npm i eslint@5.6.0. I hope that this will be helpful for you. Also, you can delete your node_modules folder and then install it.
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
add a comment |
The error is an incompatibility between eslint and babel-eslint versions. To do solve this, firstly you need to remove your eslint package using npm uninstall eslint. This command will delete your eslint package. After this, you need to install the 5.6.0 version of eslint, so write this command npm i eslint@5.6.0. I hope that this will be helpful for you. Also, you can delete your node_modules folder and then install it.
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
The error is an incompatibility between eslint and babel-eslint versions. To do solve this, firstly you need to remove your eslint package using npm uninstall eslint. This command will delete your eslint package. After this, you need to install the 5.6.0 version of eslint, so write this command npm i eslint@5.6.0. I hope that this will be helpful for you. Also, you can delete your node_modules folder and then install it.
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
answered Dec 6 '18 at 11:55
Nevzat GünayNevzat Günay
39
39
add a comment |
add a comment |
What solved this for me, was that in the error message, it told me that there was eslint installed in project with 5.6.0 and another installed in users/andrew/nodemodules/eslint with a version of 4.1.6 I tried doing a npm uninstall -g eslint but that didnt work so then I just searched for all the files and folders within users/andrew/nodemodules/eslint
and deleted them, and it worked for then.
I'm not sure if this is a good way to do it, but its worked.
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
add a comment |
What solved this for me, was that in the error message, it told me that there was eslint installed in project with 5.6.0 and another installed in users/andrew/nodemodules/eslint with a version of 4.1.6 I tried doing a npm uninstall -g eslint but that didnt work so then I just searched for all the files and folders within users/andrew/nodemodules/eslint
and deleted them, and it worked for then.
I'm not sure if this is a good way to do it, but its worked.
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
add a comment |
What solved this for me, was that in the error message, it told me that there was eslint installed in project with 5.6.0 and another installed in users/andrew/nodemodules/eslint with a version of 4.1.6 I tried doing a npm uninstall -g eslint but that didnt work so then I just searched for all the files and folders within users/andrew/nodemodules/eslint
and deleted them, and it worked for then.
I'm not sure if this is a good way to do it, but its worked.
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
What solved this for me, was that in the error message, it told me that there was eslint installed in project with 5.6.0 and another installed in users/andrew/nodemodules/eslint with a version of 4.1.6 I tried doing a npm uninstall -g eslint but that didnt work so then I just searched for all the files and folders within users/andrew/nodemodules/eslint
and deleted them, and it worked for then.
I'm not sure if this is a good way to do it, but its worked.
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
answered Jan 1 at 12:22
Andrew IrwinAndrew Irwin
155317
155317
add a comment |
add a comment |
Create a file .env in your root directory.
And you can ignore the check by putting
SKIP_PREFLIGHT_CHECK=true
in .env file.
Ref: https://github.com/facebook/create-react-app/issues/5247#issuecomment-427221678
Edit: This is not the solution to this problem. It is just to ignore the error as it is discussed in the issue.
edited Feb 4 at 6:26
Vipul Rawat
184
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
add a comment |
Create a file .env in your root directory.
And you can ignore the check by putting
SKIP_PREFLIGHT_CHECK=true
in .env file.
Ref: https://github.com/facebook/create-react-app/issues/5247#issuecomment-427221678
Edit: This is not the solution to this problem. It is just to ignore the error as it is discussed in the issue.
edited Feb 4 at 6:26
Vipul Rawat
184
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
add a comment |
Create a file .env in your root directory.
And you can ignore the check by putting
SKIP_PREFLIGHT_CHECK=true
in .env file.
Ref: https://github.com/facebook/create-react-app/issues/5247#issuecomment-427221678
Edit: This is not the solution to this problem. It is just to ignore the error as it is discussed in the issue.
edited Feb 4 at 6:26
Vipul Rawat
184
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
Create a file .env in your root directory.
And you can ignore the check by putting
SKIP_PREFLIGHT_CHECK=true
in .env file.
Ref: https://github.com/facebook/create-react-app/issues/5247#issuecomment-427221678
Edit: This is not the solution to this problem. It is just to ignore the error as it is discussed in the issue.
edited Feb 4 at 6:26
Vipul Rawat
184
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
edited Feb 4 at 6:26
Vipul Rawat
184
edited Feb 4 at 6:26
Vipul Rawat
184
edited Feb 4 at 6:26
Vipul Rawat
184
184
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
answered Jan 15 at 7:55
Ankit SinhaAnkit Sinha
519611
519611
add a comment |
add a comment |
Simple delete package-lock.json and node_modules then run npm install then
npm start
else you could install
npm i eslint@5.6.0 then
npm start
enjoy your work :)
- List item
answered Feb 22 at 18:23
ManasManas
605
add a comment |
Simple delete package-lock.json and node_modules then run npm install then
npm start
else you could install
npm i eslint@5.6.0 then
npm start
enjoy your work :)
- List item
answered Feb 22 at 18:23
ManasManas
605
add a comment |
Simple delete package-lock.json and node_modules then run npm install then
npm start
else you could install
npm i eslint@5.6.0 then
npm start
enjoy your work :)
- List item
answered Feb 22 at 18:23
ManasManas
605
Simple delete package-lock.json and node_modules then run npm install then
npm start
else you could install
npm i eslint@5.6.0 then
npm start
enjoy your work :)
- List item
answered Feb 22 at 18:23
ManasManas
605
answered Feb 22 at 18:23
ManasManas
605
answered Feb 22 at 18:23
ManasManas
605
answered Feb 22 at 18:23
ManasManas
605
605
add a comment |
add a comment |
I deleted a node modules folder that contained an older version of eslint. I found this to be the easiest solution rather than changing dependencies.
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
add a comment |
I deleted a node modules folder that contained an older version of eslint. I found this to be the easiest solution rather than changing dependencies.
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
add a comment |
I deleted a node modules folder that contained an older version of eslint. I found this to be the easiest solution rather than changing dependencies.
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
I deleted a node modules folder that contained an older version of eslint. I found this to be the easiest solution rather than changing dependencies.
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
answered Oct 23 '18 at 23:25
Juan PadillaJuan Padilla
13
13
add a comment |
add a comment |
Add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
1
That does not solve the problem, it just hides the error message
– Treycos
Nov 7 '18 at 17:51
add a comment |
Add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
1
That does not solve the problem, it just hides the error message
– Treycos
Nov 7 '18 at 17:51
add a comment |
Add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
Add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
answered Oct 11 '18 at 17:00
Marcelo Ismael Mañaricua BassoMarcelo Ismael Mañaricua Basso
1
1
1
That does not solve the problem, it just hides the error message
– Treycos
Nov 7 '18 at 17:51
add a comment |
1
That does not solve the problem, it just hides the error message
– Treycos
Nov 7 '18 at 17:51
1
1
That does not solve the problem, it just hides the error message
– Treycos
Nov 7 '18 at 17:51
That does not solve the problem, it just hides the error message
– Treycos
Nov 7 '18 at 17:51
add a comment |
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
/Users/macbook/node_modules/eslint (version: 3.19.0)
Manually installing incompatible versions is known to cause hard-to-debug issues.
If prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.
To fix the dependency tree, try following the steps below in the exact order:
- Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
- Delete node_modules in your project folder.
- Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
- Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if /Users/macbook/node_modules/eslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.
P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
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! /Users/macbook/.npm/_logs/2018-11-01T15_26_42_405Z-debug.log
answered Nov 1 '18 at 15:29
BambaBamba
11
3
Congratulation, you copy-pasted the full error message, but this is not an answer
– Treycos
Nov 7 '18 at 17:52
add a comment |
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
/Users/macbook/node_modules/eslint (version: 3.19.0)
Manually installing incompatible versions is known to cause hard-to-debug issues.
If prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.
To fix the dependency tree, try following the steps below in the exact order:
- Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
- Delete node_modules in your project folder.
- Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
- Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if /Users/macbook/node_modules/eslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.
P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
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! /Users/macbook/.npm/_logs/2018-11-01T15_26_42_405Z-debug.log
answered Nov 1 '18 at 15:29
BambaBamba
11
3
Congratulation, you copy-pasted the full error message, but this is not an answer
– Treycos
Nov 7 '18 at 17:52
add a comment |
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
/Users/macbook/node_modules/eslint (version: 3.19.0)
Manually installing incompatible versions is known to cause hard-to-debug issues.
If prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.
To fix the dependency tree, try following the steps below in the exact order:
- Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
- Delete node_modules in your project folder.
- Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
- Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if /Users/macbook/node_modules/eslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.
P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
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! /Users/macbook/.npm/_logs/2018-11-01T15_26_42_405Z-debug.log
answered Nov 1 '18 at 15:29
BambaBamba
11
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "5.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
/Users/macbook/node_modules/eslint (version: 3.19.0)
Manually installing incompatible versions is known to cause hard-to-debug issues.
If prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.
To fix the dependency tree, try following the steps below in the exact order:
- Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
- Delete node_modules in your project folder.
- Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
- Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.Check if /Users/macbook/node_modules/eslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.
P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
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! /Users/macbook/.npm/_logs/2018-11-01T15_26_42_405Z-debug.log
answered Nov 1 '18 at 15:29
BambaBamba
11
answered Nov 1 '18 at 15:29
BambaBamba
11
answered Nov 1 '18 at 15:29
BambaBamba
11
answered Nov 1 '18 at 15:29
BambaBamba
11
11
3
Congratulation, you copy-pasted the full error message, but this is not an answer
– Treycos
Nov 7 '18 at 17:52
add a comment |
3
Congratulation, you copy-pasted the full error message, but this is not an answer
– Treycos
Nov 7 '18 at 17:52
3
3
Congratulation, you copy-pasted the full error message, but this is not an answer
– Treycos
Nov 7 '18 at 17:52
Congratulation, you copy-pasted the full error message, but this is not an answer
– Treycos
Nov 7 '18 at 17:52
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%2f52586594%2feslint-error-on-deployment-on-local-server-of-react-web-app%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
