disable linting on yarn start
See original GitHub issueIs your proposal related to a problem?
We should have the option to disable linting on yarn start
, we already have an IDE that integrates with eslint and prettier, we use git-hooks to lint and format files on commit, it’s pretty annoying to have it on start as well and it also makes dev really slow.
Describe the solution you’d like
add a flag --no-lint
to disable all linting and purely build and serve on yarn start
Describe alternatives you’ve considered
Used patch-package
Additional context
Nothing.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Disable ESLint that create-react-app provides - Stack Overflow
One way is to eject react-scripts - by running yarn eject / npm run eject - and turn off eslint in webpack config...
Read more >eslint-plugin-disable | Yarn - Package Manager
To disable all plugins except specified ones use "disableAllExcept" flag in config settings (.eslintrc). The following config will disable all registered ...
Read more >How to disable an ESLint rule - Flavio Copes
Another way is to disable it globally for the project. In package.json you can find the eslintConfig rule, which might have some content...
Read more >How to disable ESLint for some lines, files or folders
To turn off ESLint in the whole file, you can add /* eslint-disable */ in the first line of that file. Alternatively, you...
Read more >Command Line Interface - ESLint - Pluggable JavaScript Linter
You can view all the CLI options by running npx eslint -h . eslint [options] file.js [file.js] [dir] Basic configuration: --no-eslintrc Disable use...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There seems to be a better option than completely disabling linter. Setting up
ESLINT_NO_DEV_ERRORS=true
flag in.env
file solves the problem. Found hereI just found out that on .env we can add DISABLE_ESLINT_PLUGIN=true