chore: Upgrade eslint to v9 #186
Open
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
eslint has rules about file extensions tied to the type of output of the Node project. Work with these rules by making the output "commonjs" (which is consistent with the TypeScript config anyway).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Migrate the configuration for ESLint to their new "flat config" format so that Renovate bot will quit pinging me about incompatible upgrades.
@edmundmiller, I'm really looking for your stamp of approval here since you are the one who converted the JavaScript to TypeScript and added all of the linting rules in the first place.
PR checklist
npm run lint)npm run format:check)npm run test)act -j example-usage)CHANGELOG.mdis updatedREADME.mdis updated