v1.1.0 options.name is failure

[lincenying]

This is my configuration file

{
                test: /\.(png|jpe?g|gif|svg)(\?.*)?$/,
                use: [
                    {
                        loader: 'url-loader',
                        options: {
                            name: 'img/[name].[hash:7].[ext]',
                            limit: 8192
                        }
                    }
                ]
            },

This is the generated file

v1.0.1 is ok

[insin]

Confirming the same issue, looks like name isn't getting passed along to the fallback.

[insin]

I think it's because v1.0.1 used to do this, so file-loader would pick up all the given options:

const fallback = require(options.fallback ? options.fallback : 'file-loader');
return fallback.call(this, src);

Here's a failing test for fallback.test.js showing failure to pass on the name option to file-loader by default:

    test('{undefined}', async () => {
      const config = {
        loader: {
          test: /\.png$/,
          options: {
            limit: 100,
            name: 'name-for-url-loader.[ext]',
          },
        },
      };

      const stats = await webpack('fixture.js', config);
      const { source } = stats.toJson().modules[0];

      expect(source).toMatchSnapshot();
    });

For this not to be a breaking release, would it need to support passing along all the options file-loader can take, or do what it used to do if a fallback + options aren't explicitly configured?

[hxlniada]

this is a big bug