-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Enable linting rules for ES6 imports #181
Comments
Oh man, that sounds really cool. I'm not sure exactly how that would work... some secret collaboration between the Would want to avoid re-linting dependents unless there are I'm very interested in this. Will reflect on it. I'm interested to hear from @MoOx as well, I think we might need to cooperate via some |
Actually, isn't this a consequence of the way Webpack works? Loaders are only invoked for files that change, right? |
Yes, but I think loaders can specify dependencies or something like this. To be honest I’m not very familiar with what loaders can do, but since webpack is crazy configurable, I would expect that this is possible in some hacky way. Also maybe it could be possible with a custom webpack plugin. |
Ah, right... interesting. Yeah, I'm not super-familiar with loaders, either. Good opportunity to get into it 😎 |
@benmosher you do have the ability to access the |
The Typescript loaders do this to perform type checking and diagnostics when the loaders finish. https://github.com/s-panferov/awesome-typescript-loader/blob/master/src/instance.ts Has a good example of this. @benmosher Hopefully this gives you some good direction. |
For postcss-import we got a similar issue. I solved this by providing an option to specify dependencies, see https://github.com/postcss/postcss-import#adddependencyto |
Closing in favor of #1559. |
Include TypeScript as devDependency in boilerplate output
I wanted to use eslint-plugin-import but I had to disable it because it doesn’t seem to work very well with
eslint-loader
workflow.I would very much welcome help in fixing this. I’m not sure if it’s possible, but it would be awesome to display good errors when users
import
something that doesn’t exist, or confuse named with default imports.cc @benmosher and @MoOx as maintainers of the corresponding projects
The text was updated successfully, but these errors were encountered: