Échec du démarrage de l'application React sur vscode par version ESLint

J'ai un problème que je ne peux pas résoudre. J'utilise ESLint dans VSCode pour tous mes projets. Maintenant, j'ai créé une nouvelle application de réaction, mais lorsque je l'exécute (npm start ou yarn start), elle génère une erreur.

L'application React utilise ESLint 5.12.5, est une version inférieure de la mienne. J'ai essayé de suivre les étapes de la suggestion mais ... ce n'est pas corrigé.

Quelqu'un peut-il résoudre mon problème?

J'ai essayé npm uninstall -g eslint , npm uninstall eslint , npm i ... bla..bla, supprimé mon extension ESLint dans mon VSCode et recréé l'application react. Mais l'erreur n'a pas été corrigée.
J'ai vérifié eslint -v, il a dit 5.14.1, mais dans l'avis d'erreur, vscode a dit que la version 5.16.0 est dans node-modules @@.

Ceci est un avis d'erreur complet lorsque j'essaye le yarn start ou le npm start :

> homework02@0.1.0 start E:\Extenal Code\Hoc JS\ReactJS-iViettech\homework02
> react-scripts start

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.12.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:

E:\Extenal Code\Hoc JS\node_modules\eslint (version: 5.16.0)

Manually installing incompatible versions is known to cause hard-to-debug issues.

If you would 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:

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:

5. 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.

6. Check if E:\Extenal Code\Hoc JS\node_modules\eslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.

7. 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.