-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add compability with 'import' eslint plugin #453
Comments
Okey, I found what only this one rule:
make such parsing errors. Because this module was disabled in UPDATE:
|
Could you please provide a repository to reproduce so someone can look into the cause? |
Okey, I have one. I will do it tomorrow. |
Please https://github.com/stalkerg/eslint-svelte-import-issue if you do after
This repo it's just a default project after create-svelte with a few tweaks. |
You need to add the following to your configuration. settings: {
// ...
'import/parsers': {
'svelte-eslint-parser': ['.svelte'],
'espree': ['.js'],
} https://github.com/import-js/eslint-plugin-import#importparsers |
Thanks! It's worked! Should we add this to eslint-plugin-svelte docs? |
Yeah, could you please open a PR to add it to the FAQ section? |
Description
Currently, If I add
import
plugin and this rule:it will produce errors like:
These rules are part of airbnb rules set https://www.npmjs.com/package/eslint-config-airbnb and many others.
To solve it, I tried to use
eslint-import-resolver-custom-alias
andeslint-import-resolver-jsconfig
but it's seems like breakeslint-plugin-svelte
(but it's works foreslint-plugin-svelte3
):seems like if such libs became resolvable, it's break
eslint-plugin-svelte
.As I understand, we have two options:
resolvers
forimport
plugin.eslint-plugin-svelte
.Regards,
The text was updated successfully, but these errors were encountered: