Update to use eslint9 #7876
Merged
Update to use eslint9 #7876
+1,947
−1,282
Conversation
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
Updates the package to use eslint9. This switches to a flat config file and also updates a few dependencies I generally tried to keep the existing logic and rules with this change. We can revisit these later I did end up having to make a few code changes for new errors that showed up after updating
|
@mjbvz CI is failing |
|
Look like the pipeline is using an old node version. Seeing if I can bump it to node 17 or newer |
The release pipelines should already be using this but the pr pipeline was on an old version
mjbvz
commented
Sep 29, 2025
sandy081
approved these changes
Oct 7, 2025
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.
Updates the project to use eslint 9. This switches to use a flat config instead of multiple config files. I also needed to update some of the eslint dependencies
I generally tried to keep the existing logic and rules with this change. We can revisit these later
I did end up having to make a few code changes for new errors that showed up after updating. I also have to update the PR pipeline to use node 20. The other pipeline seem to already be using node 20