no-duplicates rule with different webpack loaders

[benmvp]

I have a file that has some imports like:

import TextInputErrorExampleCode from '!raw!./TextInputErrorExample';
import TextInputErrorExample from './TextInputErrorExample';

The no-duplicates rule is considering these to be the same import even though one is code and the other is text.

Is there a configuration of the webpack resolver I can use to combat this?

Thanks!

[ljharb]

i'd recommend configuring webpack itself so that !raw! doesn't appear in your code (ie, don't use custom webpack syntax) and maybe do import TextInputErrorExampleCode from './TextInputErrorExample.raw';, and then configure the resolver for that extension.

[benmvp]

I like that idea! Probably will do something like './TextInputErrorExample.js.raw so it could apply to any file, but I like it. Thanks!

[benmosher]

@benmvp are those not both referencing the same file?

[ljharb]

@benmosher the implication i heard was that one provides the source code as text, the other parses it and provides its export.

[benmvp]

Yep what @ljharb said. I ended up not able to try it out because the webpack config change would've taken longer than the time I had. I will circle back at some point!