-
Notifications
You must be signed in to change notification settings - Fork 4.4k
AirBNB linter results in "Unable to resolve path to module" errors for Vue files #144
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
Comments
I get the same. Template with airbnb profile is broken :( |
This seems like a bug in airbnb/javascript, since Webpack is indeed able to resolve the path to the module. What would be the ideal solution for users of this linting config? A few ideas:
|
+1 ... Not really understand your guide @chrisvfritz? I'm assuming you mean there's an error in 'airbnb-base' which the .eslintrc.js extends? In that case has someone opened an issue, and if so can we reference it here? |
I've just disabled the rule, since Webpack will already let you know if a module can't be resolved. a5008e6 |
Disable rule `import/no-unresolved` vuejs-templates/webpack#144 See merge request !1
I created a gist which resolves this |
When i run

and then
I have the following issues

I think they come from f9f69e1, i made the same before this commit without errors and it's happen when i select AirBNB linter.
The text was updated successfully, but these errors were encountered: