Option to disable ESLint in specific contexts (but not everywhere)
See original GitHub issueIs your proposal related to a problem?
On my project, ESLint’s feedback is most valuable from 1) our editors, and 2) CI. It’s not very useful when lint errors appear in the browser when connected to the dev server. (in fact, it slows me down!)
Describe the solution you’d like
I’d like to disable ESLint in the dev server, without affecting how ESLint behaves in other contexts. (e.g., eslint
on the command line and in VS Code should be unafffected).
This could be via an environment var, e.g. DISABLE_LINT=1 react-scripts start
.
Describe alternatives you’ve considered
I’ve looked through react-script’s webpack config to check if there was already a way to do this, but couldn’t find one: https://github.com/facebook/create-react-app/blob/027b03ba8d689e619a912ed0d72c3a11ef22ac2f/packages/react-scripts/config/webpack.config.js#L749-L767
I’ve also looked into whether there was already a global disable available from ESLint or its webpack plugin, and couldn’t find anything.
Additional context
I know CRA aims to limit the available configuration options, but it seems reasonable for this one to go in Advanced Configuration.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:33
- Comments:11 (4 by maintainers)
Top GitHub Comments
I have a terrible, no good, really bad workaround: use an executable
.eslintrc.js
file and emit config conditionally.It’s not a true disable, but you can make it do very nearly nothing:
Note that you can’t ignore all files lest ESLint get upset, with an error like
All files matched by '/foo/bar/src/.' are ignored.
, but you can drop in an empty dummy file to placate it.Hey its there’s a simple solution to fix this in cra4, check out my guide on this topic(for cra4 only).
https://gist.github.com/sahilrajput03/bdd1f1d686da2e919eac647c89d87310