We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have eslint-plugin-import-x which touts itself to have the similar set of rules but more performant than eslint-plugin-import
https://github.com/un-ts/eslint-plugin-import-x
Would it make sense for this plugin to also support or map over those eslint rules to the corresponding rules in oxlint?
The text was updated successfully, but these errors were encountered:
import-x
feat(linter): support import-x plugin name (#9074)
542bbd7
closes #8779 The `import-x` rules are the reimplementation of the `import` rules. No rules added or removed. Some eslint-plugins/configs are handling the plugin the same way. Here a snippet from a config which `next-auth` is using: https://github.com/antfu/eslint-config/blob/998887cedb0b09c5b95d08602689a2c86e6662c7/src/factory.ts#L56-L67 Could not find more places where some mapping is happening. Please have a look because I did not test it.
will be supported in the next release 🥳
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
We have eslint-plugin-import-x which touts itself to have the similar set of rules but more performant than eslint-plugin-import
Would it make sense for this plugin to also support or map over those eslint rules to the corresponding rules in oxlint?
The text was updated successfully, but these errors were encountered: