Fix compatibility issues with ESLint 9 #157
Open
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.
ESLint 9 dropped support for some legacy plugin APIs. This migrates the plugin's rules to support ESLint 9, while staying backwards compatible.
Much of the diff is whitespace changes migrating legacy function rules to the object syntax, so I suggest viewing it with hide whitespace enabled.
Notably, this does not update the plugin to use the new flat config. This plugin will still work with the new flat config, but anyone wanting to use this in a flat config will have to use this compatibility syntax:
If anyone wants to try updating the plugin to work natively with the new flat config, see: https://eslint.org/docs/latest/extend/plugin-migration-flat-config
Partially fixes #156.