-
-
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
no-unresolved not working for require #90
Comments
I'm not sure what you're expecting. The |
Marking this |
Actually, upon reflection, this seems like a good improvement on the rule, and it shouldn't be tough to add. 👍 |
Agh... on second thought, |
Ok. I understand your reasons. BTW. I has not found any plugin for resolving paths for Maybe it will be a good decision to add an additional rule like |
And support |
You make a strong case. Feels like it should be separate, though... Maybe as a setting? I'll take another look. 😄 |
Check out my PR. I adapted your alternate rule into a Why were you supporting |
Oh. It's great! Thank you very much. About an array of arguments. Yes it is using for AMD, and it should not be using for CommonJS. I realized it after commit only :-) |
Added support for AMD via |
🍻 |
Hello!
Thank you for your job.
My file:
When executing
eslint --no-eslintrc --parser babel-eslint --plugin import --rule '{"import/no-unresolved":2}' test.js
I get only one error for import declaration:
The text was updated successfully, but these errors were encountered: