-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Why I am getting error no-named-as-default #425
Comments
Sorry, did not fully digest your post. You should specify "settings": {
"import/extensions": [".js"],
"import/resolver": {
"webpack": {
"config": "webpack/webpack.config.base.js"
}
}
}, This will be the default in v2+. |
Hmm that doesn't seem to fix the issue, because now i have other error:
|
Yep, sorry, I jumped the gun on my initial response. Try the updated edit with |
Now we are back to the original error :/ |
Strange. Can you provide the relative paths of the source, |
Would be helpful if you can confirm what |
@benmosher https://github.com/sqal/eslint-import-bugs If you would take a look at this, i would very much appreciate it btw. i checked verions of installed eslint plugins, and all matches with versions in package.json |
It's worth noting that the Webpack resolver technically doesn't support Webpack 2 (yet: #265), though that doesn't seem to be the issue. |
Yeah, i checked with webpack 1.x and errors are the same unfortunately |
I think this can be closed now since I no longer have any errors after updating all dependencies to the latest version :) |
@sqal How did you get it to check the imports on vue files? |
Here's my eslint config:
|
OMG! It works! Had to use the |
Thanks @sqal ! |
Hi. I have some issue with the plugin and here's what is happening:
app/index.js
components/App is
.vue
file, which looks like below:But when I import some default export from
.js
file there is no error like that, so this bug(?) seems to be related to files with.vue
extension. Any idea how i can fix this? Thanks.My config:
package.json
.eslintrc
The text was updated successfully, but these errors were encountered: