Skip to content
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

linter: import/named is unstable #7996

Open
shulaoda opened this issue Dec 18, 2024 · 1 comment
Open

linter: import/named is unstable #7996

shulaoda opened this issue Dec 18, 2024 · 1 comment
Labels
A-linter Area - Linter C-bug Category - Bug

Comments

@shulaoda
Copy link
Contributor

shulaoda commented Dec 18, 2024

Related to rolldown/rolldown#3169

Repo: https://github.com/shulaoda/repo-cases/tree/oxc/linter-import-named

The import/named rule seems to be unstable.

  ! eslint-plugin-import(named): named import "createApp" not found
   ,-[examples/basic-vue/index.js:1:10]
 1 | import { createApp } from 'vue'
   :          ^^^^^^^^^
 2 | 
   `----
  help: does "vue" have the export "createApp"?

This change seems to have been introduced in oxlint v0.15.0. I suspect it might be a regression caused by the fix for import/namespace.

@shulaoda shulaoda added A-linter Area - Linter C-bug Category - Bug labels Dec 18, 2024
@shulaoda
Copy link
Contributor Author

Actually, if you clone rolldown and enable import/named in .oxlintrc.json, then run pnpm lint-code, this issue may occur intermittently. Sometimes it throws an error, and other times it doesn’t — it's quite strange!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter C-bug Category - Bug
Projects
None yet
Development

No branches or pull requests

1 participant