ERROR in Plugin "react" was conflicted between "package.json » eslint-config-react-app » C:\Users\asus\desktop\google-clone\node_modules\eslint-config-react-app\base.js" and "BaseConfig » C:\Users\asus\Desktop\google-clone\node_modules\eslint-config-react-app\base.js". #4186

Shobit1502 · 2021-12-17T19:36:51Z

Recently get this error. plz let me know how to fix this.

HusseinHamidani · 2021-12-18T02:44:37Z

There is a conflict in the casing

C:\Users\Ruben|desktop\reactapp\test.... whereas the nodemodules is looking for C:\Users\Ruben|Desktop\Reactapp\test....

This is a windows specific problem, and previously react would have run the app regardless of this difference. Not anymore it seems.

The solution I used was to locate the folder and open with code; that ensures that the path matches directly with what is stored in node modules

backflush · 2021-12-20T00:50:48Z

Open the package.json and type ctrl + s and it disappears.

pnrede366 · 2021-12-22T05:20:22Z

Open the package.json and type ctrl + s and it disappears.

thanks

Adecodess · 2022-01-06T21:03:24Z

hi all i am having this error in production , locally when I press ctrtl + s, it disappears but when I refresh the page it comes back

NickersWeb · 2022-01-08T17:51:33Z

Have the same issue...

harish-sethuraman · 2022-01-08T18:37:10Z

This repo is for react documentation.

Support requests filed as GitHub issues often go unanswered. We want you to find the answer you're looking for, so we suggest the following alternatives:

Coding Questions
If you have a coding question related to React and React DOM, it might be better suited for Stack Overflow. It's a great place to browse through frequent questions about using React, as well as ask for help with specific questions.

https://stackoverflow.com/questions/tagged/react

Talk to other React developers
There are many online forums which are a great place for discussion about best practices and application architecture as well as the future of React.

https://reactjs.org/community/support.html

Also if you find this to be a bug feel free to raise an issue at https://github.com/facebook/create-react-app/issues

shreyash510 · 2022-01-10T07:13:23Z

delete package.json and install again

Kenramiscal1106 · 2022-01-11T00:43:51Z

Recently get this error. plz let me know how to fix this.

Are you using bash? Because bash doesn't care about the letter case of the path. This can be fixed by changing the path of your project in bash. You must reference the exact case of the path of your project

Example:
Documents is not equal to documents
Documents must be also Documents

cd
cd [project path]

tekeoglan · 2022-01-11T16:43:18Z

Recently get this error. plz let me know how to fix this.

Are you using bash? Because bash doesn't care about the letter case of the path. This can be fixed by changing the path of your project in bash. You must reference the exact case of the path of your project

Example: Documents is not equal to documents Documents must be also Documents

cd cd [project path]

You are right. I had the same issue when executing 'npm start' command on bash then i switched back to cmd the error has gone. Thank for your point.

calmb · 2022-01-12T11:54:04Z

hi all i am having this error in production , locally when I press ctrtl + s, it disappears but when I refresh the page it comes back

same here.

kdany25 · 2022-01-12T12:59:47Z

i have same issue. i do ctr+s but when i refresh it comes back

johannes67890 · 2022-01-13T21:49:56Z

I had some trouble with this as well. What I did to fix it was to upgrade nodejs to V.16. I found the bug while on V.15.
I don't know if that is the best solution, but that is how I fixed it.

SATYAM1548 · 2022-01-14T20:32:07Z

johannes67890 bro this worked thanks alot.

enderandpeter · 2022-01-16T20:12:50Z

Ran into this problem today and it turned out that the esLintConfig setting I had for extends: [react-app] was conflicting with the settings from the eslint-config-react-app package. Removing the esLintConfig resolved the issue.

igortas · 2022-01-16T20:30:47Z

Ran into this problem today and it turned out that the esLintConfig setting I had for extends: [react-app] was conflicting with the settings from the eslint-config-react-app package. Removing the esLintConfig resolved the issue.

try to update setupTests.ts with this import statement: import @types/jest. I've tried this also on monorepo w/ Lerna with --hoist option turned and it works for me

briandgomez · 2022-01-17T05:11:12Z

I got the same issue. You can try using:
C:\Users\asus\Desktop\google-clone\node_modules\eslint-config-react-app\base.js
instead of
C:\Users\asus\desktop\google-clone\node_modules\eslint-config-react-app\base.js
That's what worked for me using git bash on my windows computer

kdany25 · 2022-01-17T07:24:13Z

hello me all i did was to update the babel-eslint and u also updated .eslintrc and it worked for me

igortas · 2022-01-17T09:11:25Z

Also other solution is to set skip flag before star script: DISABLE_ESLINT_PLUGIN=true, in case u have custom .eslintrc file

karthikuppalapati · 2022-01-19T15:02:02Z

I too had the same issue. I am using Visual Studio Code.

E:\React-Projects\playground\test-7>. Here test-7 is my project folder created using create-react-app. The folder playground actually starts with a capital p instead of small p in my laptop. I changed playground to Playground it worked!!!

E:\React-Projects\Playground\test-7> This the changed version of my folder name

ceyhun-yildiz · 2022-01-24T11:38:00Z

I am using Bash and I have changed desktop to Desktop on my path and it works without the error now

ShawnNJH · 2022-01-25T07:42:38Z

instead of "saving" your package.son everytime you make an update, go to your package.json and delete the following

"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},

Cheers! :)

Kenramiscal1106 · 2022-01-25T08:18:49Z

Still didn't work

d1joseph · 2022-01-27T01:16:39Z

For those looking for the open issue - facebook/create-react-app#11825

SuzieZUMO · 2022-01-27T21:48:36Z

Recreate your projects in lower case. Solution name case doesn't matter.
Renaming project names won't help (perhaps renaming folder names to lower case would, I didn't try).

EddisonM · 2022-01-30T07:32:26Z

This is the solution:

Use the correct App path location.

For example if u are in C:\users\cyber\documents\juego_gabriel> and run "npm start", u get the next error:

To fix it follow these steps:

Locate your project folder location
Copy that path and paste in your VS Code PS Terminal (run "cd [path]")
Run "npm start"

Done...!!!

PD: The error is the wrong uppercase/lowercase letters in your project path location.

ghost · 2022-02-01T19:56:55Z

The problem is Windows PowerShell.
I don't recommend Windows PowerShell.
Make a download the last version of Powershell from Microsoft Store and will works fine

.

wevertonbezzera013 · 2022-02-17T14:23:56Z

Open the package.json and type ctrl + s and it disappears.

GOD

prettygenius · 2022-02-17T20:50:23Z

I got the same error apparently I was using the wrong path Desktop was capitalized so use cd Desktop NOT cd desktop I re ran npm start and it worked for me! Thanks guys

ninzacoder · 2022-02-25T12:46:00Z

There is a conflict in the casing

C:\Users\Ruben|desktop\reactapp\test.... whereas the nodemodules is looking for C:\Users\Ruben|Desktop\Reactapp\test....

This is a windows specific problem, and previously react would have run the app regardless of this difference. Not anymore it seems.

The solution I used was to locate the folder and open with code; that ensures that the path matches directly with what is stored in node modules

saved me a lot of hair you did.

NarayanBavisetti · 2022-03-01T15:48:04Z

It is just because of the capital letter used in the location of the file path. That's it. check it and make all the folder name to lowercase.

Nandhini-Madan · 2022-03-02T07:14:36Z

Open the package.json and type Ctrl + s and it disappears.

Thanks. I thought it was fun but it worked like a charm.

phoique · 2022-03-02T11:49:15Z

I get this error when I update my packages on my Macbook. With ctrl s the error went away but was coming back. It was fixed when I deleted node_modules and yarn.lock and created it again with yarn install.

OldTechnique · 2022-03-08T03:21:59Z

Issues is simple. exit terminal cd the correct path. when u cd'd u cd'd with the wrong case.

yaowang908 · 2022-03-13T04:02:33Z

I'm putting in my two cents, for me, the problem is a space in the path, remove the space, everything works.

bkincz · 2022-03-21T05:26:14Z

I stumbled across this issue when using a custom .eslintrc with a fresh CRA (react-scripts v5.0.0) project.

I resolved this by removing "root": true & plugin:react/recommended from my .eslintrc.

This is my .eslintrc at the moment while using CRA (react-scripts v5.0.0):

{
    "env": {
        "browser": true,
        "es2021": true,
        "jest": true
    },
    "extends": [
        "plugin:react/jsx-runtime",
        "plugin:prettier/recommended",
        "standard"
    ],
    "parser": "@typescript-eslint/parser",
    "parserOptions": {
        "ecmaFeatures": {
            "jsx": true
        },
        "ecmaVersion": 12,
        "sourceType": "module"
    },
    "plugins": ["react", "@typescript-eslint"],
    "settings": {
        "react": {
            "version": "detect"
        }
    },
    "globals": {
        "React": true,
        "google": true,
        "mount": true,
        "mountWithRouter": true,
        "shallow": true,
        "shallowWithRouter": true,
        "context": true,
        "expect": true,
        "jsdom": true,
        "JSX": true
    },
    "rules": {
        /* Rules go here */
    },
    "overrides": [
        {
            "files": ["*.ts", "*.tsx"],
            "parserOptions": {
                "ecmaVersion": 12,
                "project": ["./tsconfig.json"]
            }
        }
    ]
}

Hopefully this helps.

Code-with-Fizza · 2022-03-21T19:34:47Z

Still didn't work

Code-with-Fizza · 2022-03-21T19:36:27Z

Remove the following code from package.json ...it worked for me

"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},

dendoink · 2022-03-28T01:29:34Z

Open the package.json and type ctrl + s and it disappears.

Great thanks !

Jaynish-D · 2022-03-29T08:56:57Z

Open the package.json and type ctrl + s and it disappears.

Thanks this is help me lot.😊😊😊

Blind2k · 2022-03-30T10:40:08Z

Saving the files over and over again is not a solution.
In my case, the application's local source directory had capital letters.
Changed to lower case, and it works smoothly.

gaearon · 2022-03-30T16:37:15Z

This repository is for the React website. There is no relation between the topic you are discussing and the React website. If you have an issue with some plugin, please file it in the repo with that plugin. Thanks!

harish-sethuraman closed this as completed Jan 8, 2022

harish-sethuraman mentioned this issue Jan 23, 2022

Plugin "react" was conflicted between "package.json » eslint-config-react-app #4229

Closed

reactjs locked as off-topic and limited conversation to collaborators Mar 30, 2022

ERROR in Plugin "react" was conflicted between "package.json » eslint-config-react-app » C:\Users\asus\desktop\google-clone\node_modules\eslint-config-react-app\base.js" and "BaseConfig » C:\Users\asus\Desktop\google-clone\node_modules\eslint-config-react-app\base.js". #4186

ERROR in Plugin "react" was conflicted between "package.json » eslint-config-react-app » C:\Users\asus\desktop\google-clone\node_modules\eslint-config-react-app\base.js" and "BaseConfig » C:\Users\asus\Desktop\google-clone\node_modules\eslint-config-react-app\base.js". #4186

Comments

Shobit1502 commented Dec 17, 2021

HusseinHamidani commented Dec 18, 2021

backflush commented Dec 20, 2021 • edited Loading

pnrede366 commented Dec 22, 2021

Adecodess commented Jan 6, 2022

NickersWeb commented Jan 8, 2022

harish-sethuraman commented Jan 8, 2022 • edited Loading

shreyash510 commented Jan 10, 2022

Kenramiscal1106 commented Jan 11, 2022 • edited Loading

tekeoglan commented Jan 11, 2022

calmb commented Jan 12, 2022

kdany25 commented Jan 12, 2022

johannes67890 commented Jan 13, 2022 • edited Loading

SATYAM1548 commented Jan 14, 2022

enderandpeter commented Jan 16, 2022

igortas commented Jan 16, 2022 • edited Loading

briandgomez commented Jan 17, 2022

kdany25 commented Jan 17, 2022

igortas commented Jan 17, 2022

karthikuppalapati commented Jan 19, 2022

ceyhun-yildiz commented Jan 24, 2022

ShawnNJH commented Jan 25, 2022 • edited Loading

Kenramiscal1106 commented Jan 25, 2022

d1joseph commented Jan 27, 2022

SuzieZUMO commented Jan 27, 2022

EddisonM commented Jan 30, 2022 • edited Loading

ghost commented Feb 1, 2022

wevertonbezzera013 commented Feb 17, 2022

prettygenius commented Feb 17, 2022

ninzacoder commented Feb 25, 2022

NarayanBavisetti commented Mar 1, 2022

Nandhini-Madan commented Mar 2, 2022

phoique commented Mar 2, 2022

OldTechnique commented Mar 8, 2022

yaowang908 commented Mar 13, 2022

bkincz commented Mar 21, 2022 • edited Loading

Code-with-Fizza commented Mar 21, 2022

Code-with-Fizza commented Mar 21, 2022

dendoink commented Mar 28, 2022

Jaynish-D commented Mar 29, 2022

Blind2k commented Mar 30, 2022

gaearon commented Mar 30, 2022

backflush commented Dec 20, 2021 •

edited

Loading

harish-sethuraman commented Jan 8, 2022 •

edited

Loading

Kenramiscal1106 commented Jan 11, 2022 •

edited

Loading

johannes67890 commented Jan 13, 2022 •

edited

Loading

igortas commented Jan 16, 2022 •

edited

Loading

ShawnNJH commented Jan 25, 2022 •

edited

Loading

EddisonM commented Jan 30, 2022 •

edited

Loading

bkincz commented Mar 21, 2022 •

edited

Loading