feat: add eslint api v9 compatibility #33
Merged
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.
context.getAncestors is not a function
with eslint 9.0.0 #32Issue
Running the following in this repo (currently based on eslint@8.56.0):
npm ci npm test
results in the deprecation warning:
Change
Use the information in the blog post Preparing your custom rules for ESLint v9.0.0 from Sep 26, 2023 from the section context.getAncestors() to update the rule lib/rules/no-unused-expressions.js so that it is compatible with ESLint
v9
and with earlier ESLint versions.Verification
Deprecation
Confirm that deprecation is resolved by executing:
npm ci npm test
Verify that no deprecation warning is output and that all tests pass (81 passing).
Backwards compatibility
Install an earlier version of ESLint (
8.0.0
), before the replacement methodSourceCode#getAncestors(node)
was added, and confirm that tests continue to pass (81 passing).npm install eslint@8.0.0 npm test