eslint-config-react | ESLint React configuration for JS projects | Code Analyzer library

nodemon is for node.js it wouldn't make sense to run nodemon with React. If you're trying to use a backend service with node.js then you would run nodemon on your server file (e.g. nodemon server.js or nodemon index.js). But these should be seperate from your React app folder. For example you could have the following:

what's happening is that when you run npm start it's probably doing some checks with eslint, from what I remember create-react-app has some checks that break your build if you have eslint errors so makes sense that they're associated.

The error you're getting here is related to a node feature that eslint is using called subpath exports but it's support is hit or miss depending on how the library is consumed. This has been highlighted to cause issues when used with jest for example.

For the flowtype eslint plugin this is the exact line of code that's causing you issues.

You can also read about a similar issue reported regarding the typescript eslint plugin.

The solution and the reason I'm even able to understand what's causing this problem is that I made a fix to this yesterday in a clone of the eslint-plugin-flowtype (given that the original plugin had a lack of maintenance) here https://github.com/flow-typed/eslint-plugin-ft-flow/pull/23.

I'll raise an issue with create-react-app and see if they're willing to swap out the plugin with the new one which would have more maintenance and solve issues that you're experiencing.

Try deleting the node module folder, and again install all of them, by running npm install, or yarn, depending on the type of package manager you are using.

I had the same issue as you, and i got tired doing Ctrl + S on package.json, which is a one of the solutions. Another way to solve that is your path you have MERN (all uppercase) and the path that the error show to you have mern (all lowercase) so you can rename that folder to desktop and it will solve the problem.

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

You need to update all the packages as in the case of eslint-config-react-app's package.json it would have the previous version of create-react-app. So, basically the error is telling you that you are updating to the new version, but the other libraries in your project use another version.

Try doing - npm run update

craco's Github readme, states that it is supporting Create React App (CRA) 4.*. By this statement, I'm assuming CRA 5 is not officially supported by craco.

However, this repository utilizes both CRA 5 and craco (but I have not verified that it is working). Use this repository to compare your setup (after verifying that the linked repositry is working), and try different settings/configs to see if you get further.

Fixed by npm audit fix --force but before run, make sure it does not damage your project.

npm audit fix only modifies the dependencies that shouldn't cause problems based on SEMVER rules. The --force is a dangerious option because it upgrades the dependencies regardless of any rules. This can cause a dependency to go from version 1.2. 0 to version 2.3.

What did a npm audit fix --force change and how do you fix it?

The error message that you shared seems to be related to a bug with react-error-overlay.

react-scripts 4.0.3. uses react-error-overlay 6.0.9. However, 6.0.10 is marked as a patch, so npm uses 6.0.10 instead of 6.0.9, but 6.0.10 is not compatible with 6.0.9.

On the other hand, react-scripts 5 does not use react-error-overlay, but might be causing breaking changes with your other packages, hence the other errors.

You can find more information about the react-error-overlay bug in these issues on the CRA repository:

• Hot Reload Fails, DOM adds an additional iframe containing entire contents of the html DOM element #11880
• Is this the bug of react-error-overlay? #11773
• v5 Regression react-error-overlay build - Uncaught ReferenceError: process is not defined #11771

Here's a possible solution with react-scripts 4.0.3.:

1. In your project's package.json file:

• In dependencies, ​set the react-scripts version to 4.0.3.
• Under dependencies, in resolutions, add react-error-overlay 6.0.9.
• In devDependencies, add react-error-overlay 6.0.9.