no-deprecated rule issue with default exports

[etyrrell22]

Made a small reproduction test case here:

main...etyrrell22:eslint-plugin-import:main

I'm willing to pick this up, but want to make sure this is unexpected behavior, fixable, and not a false positive on my part.

node --version
v24.14.0

npm --version
11.9.0

[ljharb]

Does it work if the deprecation tag is on the export itself?

Either way it seems like something that should indeed warn.

[etyrrell22]

Does it work if the deprecation tag is on the export itself?

Either way it seems like something that should indeed warn.

Yup, that's the fix I'm using as a workaround

[snakefood3232]

I see you've identified an issue with the no-deprecated rule and default exports in your test case. I'd handle this by reviewing the rule's handling of default exports and implementing adjustments to correctly identify deprecated patterns. Can have a PR up in 2-3 days. Having solved similar linting issues in other projects, I'm confident in addressing this efficiently.

[snakefood3232]

I see you're experiencing issues with the no-deprecated rule and default exports based on your test case. I'd handle this by reviewing the current rule logic to ensure it accurately differentiates default exports and doesn't trigger false positives. I can have a PR ready within 2 days. I've worked on similar issues in rule validation for other ESLint plugins, ensuring precise and expected behavior.

[snakefood3232]

I see you're encountering an issue with the no-deprecated rule regarding default exports in your test case. I'd handle this by reviewing the rule logic to ensure it correctly identifies deprecated exports, whether they're named or default. I'll also add test cases for both scenarios to prevent future regressions. I can have a PR up in 2 days. I've dealt with similar ESLint rule configurations and fixes in other projects, ensuring comprehensive linting compliance.