Draft
Conversation
This was referenced May 28, 2025
Collaborator
|
Chatted with @RayBB , this has become tricky! Having different flows for how eslint runs in CI vs locally would be a bit frustrating to maintain; hopefully one of the other repos has an idea/solution! Otherwise I think sticking with the older eslint for now might be good enough. I'm sure they'll sort it out eventually, at which point we can update 😁 In the mean time, it might be worth look at oxc; that's a newer player in this space, not sure if it can do everything we're using eslint for, but might be worth a look! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #10805
TODO:
@eslint/jswhich is used by the new configTechnical
It seems pre-commit and eslint and node modules don't work well together. So it's in a bash script now.
See:
Testing
Screenshot
Stakeholders