Local .eslintrc.json ignored in 6.0.0
See original GitHub issueHere’s my test project, simply clone it and install dependencies.
Running npm test
or npm run lint
works fine. Now go to the package, upgrade gulp-eslint
dependency to 6.0.0
, and nothing works anymore, producing tons of linting errors. It looks like from version 6.0.0 the local .eslintrc.json
files are ignored.
Any idea how to fix it and/or change the project to make it work with version 6.0.0?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5
Top Results From Across the Web
ESLint fails to load plugins when using ESLint 6.x #696 - GitHub
I'm using TypeScript + Yarn workspaces + Lerna and have all the plugins installed locally and globally . Failed to load plugin prettier:...
Read more >eslint-plugin-vue - Gitter
@plakhin ESLint now tries to resolve all plugins as local installs as of 6.0.0. In your case the issue sounds like an extra...
Read more >My create-react-app is failing to compile due to ESLint error
This flag is ignored during production and when they are any git hooks ... We are going to add another script to our...
Read more >Configuration Files - ESLint - Pluggable JavaScript Linter
json files should not include them). You can use JavaScript-style comments for JSON files and YAML-style comments for YAML files. ESLint safely ignores...
Read more >gulp-eslint | Yarn - Package Manager
A gulp plugin for processing files with ESLint. gulpplugin, eslint, gulp ... gulp-eslint Build Status Coverage Status ... Bump eslint dependency to ^6.0.0...
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
And holy crap, here it is:
This is all in the README, and I’m super embarrassed that I was too impatient to read it.
Adding this makes it work: