This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
[Feature Request] [Linter] Adopt eslint-plugin-deprecation #2898
Labels
You can continue the conversation there. Go to discussion →
This is a feature request to adopt the eslint-plugin-deprecation plugin/rule.
The
import/no-deprecation
plugin catches far fewer deprecation errors than the plugin mentioned above- I created a sample project here that shows multiple deprecated files in-use that are not caught by oxlint OR eslint.The
deprecation/deprecation
rule is also one of the slowest in our current CI flow, so it would make a HUGE quality of life difference if we could offload it to oxlint.Example timings from two projects:
Thanks!
The text was updated successfully, but these errors were encountered: