It's important to note that any rules that are set to "error" will stop the project from building.When working with TypeScript, you'll need to provide an overrides object for rules that should only target TypeScript files.We highly recommend extending the base config, as removing it could introduce hard-to-find issues.You can extend our base ESLint config, or replace it completely if you need. Extending or replacing the default ESLint config If you want to enforce a coding style for your project, consider using Prettier instead of ESLint style rules. This is because Create React App intentionally provides a minimal set of rules that find common mistakes. They won’t affect the terminal and in-browser lint output. Note that even if you customise your ESLint config, these changes will only affect the editor integration. If you prefer the lint results to appear right in your editor, please make sure you install an ESLint plugin/extension. You should see the linter output right in your terminal as well as the browser console. Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint. It works out of the box for newly created projects with and higher. Note: this feature is available with and higher. Some of the most popular editors are covered. To configure the syntax highlighting in your favorite text editor, head to the relevant Babel documentation page and follow the instructions. Here's a few tips to maximize your productivity: Syntax highlighting Create React App comes with a bunch of tools that improve the editing experience - if configured correctly.
0 kommentar(er)
