-
Notifications
You must be signed in to change notification settings - Fork 2k
fix: exports for eslint-config-turbo
#9978
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
eslint-config-turbo
### Description Mis-mapped the exports conditions in package.json. 🤦
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry if this is the wrong spot for this, but it helped resolve an issue. When I upgraded from turbo@2.4.2 to 2.4.4 my eslint config broke while following the listed docs for legacy usage.
I updated to use this files extends
and my eslint config was resolved.
Old:
extends: ["turbo"]
Resulted in:
eslint-config-turbo is invalid:
- Unexpected top-level property "default".
Should the docs be updated to suggest using this instead?
New:
extends: ["plugin:turbo/recommended"]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry for tagging @anthonyshew, because this is important for people that not using eslint flat config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries. Thanks for the tag. Will fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's the fix: #10105
Sorry about that!
This includes the turbo plugin correctly following [this comment](vercel/turborepo#9978 (comment)) from a user experiencing the same issue we encountered in #3337
Description
Mis-mapped the exports conditions in package.json. 🤦