Support ESLint 7
See original GitHub issueHi! 👋
Do I assume correctly that ESLint 7 isn’t supported yet? I’m looking at the fact that eslint
’s version range in dependencies
doesn’t include 7. (If eslint
were a peer dependency, I’d get a stronger signal; there would be a peer-dep warning at install time if I didn’t depend directly on a valid version of eslint
.)
If so, here’s an issue for it! 🙂
I suspect there would be more work involved than just #397 (or #345, #355, #360, #368, #369, #377, or #388), but I’m not sure.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Migrating to v7.0.0 - ESLint - Pluggable JavaScript Linter
To address: Make sure you upgrade to at least Node.js 10.12.0 when using ESLint v7.0.0. One important thing to double check is the...
Read more >7.0.0 - eslint - npm
An AST-based pattern checker for JavaScript.. Latest version: 8.30.0, last published: 8 days ago. Start using eslint in your project by ...
Read more >Support ESLint 7.x · Issue #223 · mysticatea/eslint-plugin-node
It would be awesome to have official ESLint 7 support. I'm happy to help where I can of course. The text was updated...
Read more >ESLint 7.0, 7.1, 7.2 Releases Improve Developer Experience ...
The recent ESLint 7.0, 7.1, and 7.2 releases introduce numerous developer experience improvements, remove support for Node.js version 8, ...
Read more >ESLint - Code Climate
To use ESLint version 5, 6, or 7 for analysis, specify a channel within your .codeclimate.yml ... We hope to build support for...
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
#407 has been merged, fixing this, so I’ll go ahead and close. Thanks, @cy6erskunk, @hamzahamidi, and @zimme! 🎉
Well, @chrisbobbe, the only tests failing on the PRs you listed are the ones using Node 8! So, it very well could be easy and just work.
I think we’re open to a PR that:
engines
field inpackage.json
accordingly (only look for a floor please, not a ceiling)