-
-
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
Lint Dynamic Imports for no-unresolved #1035
Comments
Seems reasonable, altho it would require using babel-eslint. |
Actually tho - import() uses urls, not paths, so I’m not sure how this would work properly. |
Doesn't it use paths and webpack transforms them into urls? I've also noticed that |
|
- fix import() to work with no-cycle - add tests using multiple imports in no-cycle Fixes import-js#1035. Fixes import-js#1166.
For code-splitting in our app we have
However, we don't get the same awesome eslint error if that path doesn't exist. It would be great to have that linted as well.
The text was updated successfully, but these errors were encountered: