@Sparki2002 PR welcome 👍

I want this feature too.

This feature would be really nice.
Does anybody know a workaround? E.g. somehow wrapping file-loader with predefined options or something similar?

@Sparki2002 I found that you can set any fallback options like this:

{
  test: /\.(woff|woff2|eot|ttf|svg)$/,
  use: {
    loader: "url-loader",
    options: {
      limit: 8192,
      fallback: "file-loader",
      
      // Below are the fallback options
      name: isProd ? "[hash:7].[ext]" : "[name].[ext]",
      publicPath: "/fonts",
      outputPath: "fonts"
    }
  }
}

Works great, thanks @fengcen!

@evilebottnawi: I think adding this to the readme would be helpful for future users.

I believe, that also it would be good to have feature to chain fallback loaders.
Usage example:

• I want my small pictures to be loaded as url-string
• I want my bigger pictures to be optimized

So I need this code:

...
test: /\.(gif|png|jpe?g)$/,
  loader: 'url-loader'
  options: {
     limit: 1000,
     fallback: [
       'file-loader',
       {
         loader: 'image-webpack-loader'
         options: {
           // ...optimizing options
         }
       }
     ]
   }
}

@queses no, please read how works loaders

@fengcen @TimHolzherr yep, feel free to send PR

Hey @evilebottnawi watch out: I don't see the default fallback=file-loader to be respected, just lost 1 hour on this to find out I had to explicitly set it like this (I'm on [email protected]):

{
    test: /\.(woff|woff2|ttf|eot)$/i,
    use: [{
        loader: 'url-loader',
        options: {
            limit: 8192,
            fallback: 'file-loader',
            outputPath: '/assets/fonts',
            name: '[name].[ext]?hash=[hash]',
        },
    }],
}

@damianobarbati can you create new issue with minimum reproducible test repo?

good