• Operating System: OSX 10.15.2
• Node Version: v10.1

Beware of the fact that errors are written to stderr and everything else is written to stderr (or stdout if logInfoToStdOut is true).

that errors are written to stderr and everything else is written to stderr

So is everything written to sderr ?
I don't understand here ? Is there something that I'm missing?

That's in the docs/ README.

A pull request by @vankop was merged and maintainers requested a documentation change.

See pull request: webpack/webpack#10557

Haven't seen this reporter anywhere, tried out alpha 27 and with workerize-loader I get this:

TypeError: this.cache.get is not a function
    at /Users/nw/projects/motion/orbit/node_modules/webpack/lib/Compilation.js:2186:18
    at arrayEach (/Users/nw/projects/motion/orbit/node_modules/neo-async/async.js:2405:9)
    at Object.each (/Users/nw/projects/motion/orbit/node_modules/neo-async

svg-sprite-loader is good loader for svg.

But the example custom-runtime-generator only include React.

I create a repo for use svg-sprite-loader in vue through runtime-generator.

Please see this repo: https://github.com/Akimyou/svg-sprite-vue-generator

But i want to add some example in svg-sprite-loader main repo or in docs, can U give me some suggestion about it?

I've reached this loader from webpack official page. It was mentioned as an example of loaders using pitch function. The idea of pitch function is clear but I can't understand the purpose of this loader. Can I simply use require.ensure instead of it? Would you please improve readme or just explain me an idea and I'll make a PR myself.

Readme suggests require.resolve as a way to get path to a module, but webpack's resolution differs from node's one (e.g. webpack supports module property).

Please update readme with info about how to properly get module path.

The documentation for imports-loader has a case for injecting a variable with a JS Object literal as follows:

import?config=>{size:50}

This works great, but once you try to add another property to this JS object in (what I considered to be) the obvious way:

import?config=>{size:50,color:2}

The imports-loader (indirectly via loaders-util) tokenizes on the comma and starts doing.

Automatically add class name to <svg> tag from its svg file name.

What does the proposed API look like?

A file named logo.svg :

<svg class="foo" viewBox="0 0 25 25">
    <path d="..."/>
</svg>

The options :

  {
    test: /\.svg$/,
    loader: 'svg-inline-loader',
    options: {
      className: 'icon-[filename]',
      // or
      // classPrefix: 'icon

Hi,

I'd like to contribute to improving the documentation for this great plugin.

It's only a detail but I haven't been able to find in the docs that if some sizes are set like [300, 600, 1200], the first one will be the one used for src attribute. So in my case, IE was using the 300px image instead of the bigger one. To fix this I had just to put 1200 as the first array element.

Could

My team and I ran into a production issue where we were not passing the results of vue-svg-loader to babel-loader. This caused a production issue with IE11. After reading the documentation a bit more carefully, it looks like babel-loader is implicitly used throughout to docs.

Would there be a benefit to adding a brief snippet of documentation stating that the loader requires babel to be