no-extraneous-deps: strip out webpack loaders from imports

[donaldpipowitch]

As far as I know I can only ignore imports with webpack loaders, but I'd like them to be supported in certain rules.

E.g. I have something like this:

'import-inject-loader?showNotification!..' should be listed in the project's dependencies. Run 'npm i -S import-inject-loader?showNotification!..' to add it (import/no-extraneous-dependencies)

With an import like import {} from 'import-inject-loader?showNotification!../../src/form/FormModel';. But it would be nice, if it would just be treated as import {} from '../../src/form/FormModel'; natively.

[alexgorbatchev]

I think a custom resolver here could help. Have a loot at https://github.com/alexgorbatchev/eslint-import-resolver-typescript/blob/master/index.js and you could probably make one. What do you think?

[donaldpipowitch]

This sounds interesting. I need to look into that. Thank you.

[benmosher]

@donaldpipowitch are you using the Webpack resolver? It should be stripping loaders already.

[benmosher]

ohhhhh wait, this is for no-extraneous-deps. got it. I don't think the resolver can save you from this one (yet).

[benmosher]

making a note for myself: need to add a sanitize method to the resolver API.

[RayBenefield]

Running into a similar kind of problem by using the Alle monorepo style (https://github.com/boennemann/alle). I don't want to have to list the node_modules that exist in the project. And while a custom resolver solves no-resolve it doesn't solve no-extraneous-dependencies. Something that allows me to specify a directory for no-extraneous-dependencies to filter out would be golden.

[alexkrautmann]

I'm also having this issue. Right now inject-loader is the only way I have to mock out module deps in my webpacked app. I really don't want to completely disable no-extraneous-dependencies or import/first.