fix: plugin name to match naming convention#81
Open
Conversation
43081j
previously approved these changes
Mar 16, 2026
Contributor
|
this will break oxlint support we are blocked until oxc-project/oxc#20440 |
Author
|
@43081j, I just tested it, and it looks like everything works. oxlint-migrate renamed the rules from I think we can just update the documentation for oxlint. It’s ok for a major version 0 of the package. |
Contributor
|
that will break ESLint where the rules are im pretty sure you can't fix this and oxlint needs to support |
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
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.
Changes
meta.nameandmeta.namespaceproperties so it follows the ESLint plugin naming convention (same approach as @typescript-eslint/eslint-plugin).This is also necessary so that oxlint-migrate can name the package correctly.
Before: eslint-plugin-e18e
After: @e18e/eslint-plugin