How react shuts down eslint

This article mainly introduces "how react shuts down eslint". In daily operation, I believe many people have doubts about how react closes eslint. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "how react shuts down eslint". Next, please follow the editor to study!

Method: 1, the use of "npm run eject" to copy all dependent files and the corresponding dependencies to the project; 2, in the "package.json" to modify the "eslintConfig" project code; 3, if the lack of dependencies, the need to reinstall dependencies, use "npm start" to restart the project.

The operating environment of this tutorial: Windows10 system, react17.0.1 version, Dell G3 computer.

How does react shut down eslint?

Step 1: npm run eject

Npm run eject

Npm run eject will copy all dependent files and corresponding dependencies (webpack, babel, etc.) to your project. Is an one-way operation, once eject, the operation of npm run eject is irreversible

Step 2: modify the code in package.json

"eslintConfig": {"extends": "react-app", "rules": {"no-undef": "off", "no-restricted-globals": "off", "no-unused-vars": "off"}}

Step 3: restart the project

Npm start

If there is a lack of dependencies, reinstall the dependencies.

At this point, the study on "how react shuts down eslint" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!