Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
83 files changed, and most were deletions of eslint-related items and / or config files |
…pass don in the fuel sdk
cprussin
approved these changes
Feb 10, 2026
Collaborator
cprussin
left a comment
There was a problem hiding this comment.
Hard to look at this in depth given how much is being changed (much of it just reformatting) but scrolling through things look good to me... we spoke offline and I think we're ok to move forward on this as long as we can be around to support if anything comes up that we didn't anticipate.
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
2 participants
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.
Summary
Replaced ESLint with biome, which now handles linting and formatting of all JS, TS, CSS and JSON code (not yet SCSS)
Rationale
ESLint is slow, configuring it has turned into a major pain, and you often have to have 1 million plugins and extensions to get it to do what you want.
We've already performed this migration in another repository here, so this is a feature-parity PR to match prior workstreams here.
How has this been tested?