-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
import-x/no-extraneous-dependencies
settings not applying to custom files
#91
Comments
Having the same issue. The rule stopped working for some reason, since I remember it did work. |
I managed to debug it to the settings: {
"import-x/resolver": {
typescript: true,
node: true,
},
}, to the ESLint configuration, exactly as recommended in the Readme. However, the required package throws the following warning in
So, it's not declared as a compatible one with the |
Related issue regarding that warning message: import-js/eslint-import-resolver-typescript#293 Workaround: import-js/eslint-import-resolver-typescript#293 (comment) |
Workaround for the related issues: - un-ts/eslint-plugin-import-x#91 - import-js/eslint-import-resolver-typescript#293
Steps to reproduce
test.config.ts
file, import a dependency defined indevDependencies
in package.jsonWhat's expected?
No error is logged, since the file is allowed to import dependencies from
devDependencies
What happens?
The rule reports an error
Additional context
Upstream doesn't have this issue, so switching back to the original plugin will demonstrate the expected behaviour of this rule.
The text was updated successfully, but these errors were encountered: