Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

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

[Feature Request] [Linter] Adopt eslint-plugin-deprecation #2898

Closed
MIreland opened this issue Apr 5, 2024 · 0 comments
Closed

[Feature Request] [Linter] Adopt eslint-plugin-deprecation #2898

MIreland opened this issue Apr 5, 2024 · 0 comments
Labels
A-linter Area - Linter E-Help Wanted Experience level - For the experienced collaborators

Comments

@MIreland
Copy link

MIreland commented Apr 5, 2024

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:
image

image

Thanks!

@Boshen Boshen added A-linter Area - Linter E-Help Wanted Experience level - For the experienced collaborators labels Apr 6, 2024
@oxc-project oxc-project locked and limited conversation to collaborators May 18, 2024
@Boshen Boshen converted this issue into discussion #3339 May 18, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
A-linter Area - Linter E-Help Wanted Experience level - For the experienced collaborators
Projects
None yet
Development

No branches or pull requests

2 participants