Permit Loader Specification Or Relax ESLint webpack loader rule

[cdaringe]

Hi all,

I'd like to revisit #1015.

I have the need to serve some raw files for download and to render in plaintext.

That is, I want to import plaintext JS in some cases, and I also want to be able to serve JS downloads. The issue as described in #1015 prevents me from achieving this.

I know it's niche, but a generic file is a 1st class citizen, IMHO. Unfortunately we need some access to the underlying tooling to specify the intended consumption. Requires & import statements will be piece of cake migrations 🍰 if we de-webpack.

[gaearon]

In cases where you want to import plaintext, why not just use JS for this?

export default `
  any plaintext
  you like
`;

[cdaringe]

sure, but i also want to serve it for download (i can blob it, but would rather URL to it) and in some cases, actually use it as a component too! it's nutty! :)

im okay // eslint-disable-lineing for now.

[gaearon]

Yea, the problem is it’s not really supported, and we don’t promise even patch version changes are safe. So we can break you in any version accidentally.

[cdaringe]

definitely. i have moderate confidence that webpack will be in here for a while & that file & url loaders will be sticking around too, so im gettin wild and taking a risk!

[cdaringe]

#tests