It doesn't work with eslint v8
See original GitHub issueVersions:
prettier-eslint
version: 9.0.2node
version: 14npm
(oryarn
) version: 1.22.5
Have you followed the debugging tips?
Yes
Relevant code or config
prettier-eslint '**/*.{ts,tsx}' --list-different
What I did:
What happened:
Reproduction repository:
Problem description: It doesn’t work with eslint v8
Suggested solution: update with this document to adapting eslint v8.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:20
- Comments:12
Top Results From Across the Web
Does not work with ESLint v8 (ESLint: Invalid Options ... - GitHub
I have started a new project and VS Code ESLint (v2.2.3) would not work. This message popped up. ESLint from console was working...
Read more >Migrating to v8.0.0 - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >ESLint v8.0.0 released - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >What's coming in ESLint v8.0.0 - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >ESLint v8.16.0 released - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
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
🎉 This issue has been resolved in version 14.0.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
Man, that’s a bummer. Even on the webpack core team we had mechanisms for other non-core individual teams and groups of collabs to talk to one another. I would have thought the Prettier org would be more organized given how huge the project is within the developer community these days. But thanks for the clarification.
Way ahead of you. But that doesn’t mean that I’m not going to stop trying to help the larger Atom community.