same question.

it is not a bug, you can add a query parameter name=xxx like this

    {
                test: /\.(png|jpg)$/,
                loader: 'url-loader?limit=100000&name=./imgs/[hash].[ext]'
    }

see loader-utils source code

If you want for example emit your files at fonts/some-font.ttf
loader: "file?name=./fonts/[hash].[ext]"
But you are already extracting your css into css/styles.css
new ExtractTextPlugin('css/app.css', { allChunks: true })

Your css files will try load the fonts from css/fonts/...
Because they expect to be in the root of the public folder.

You can fix this by giving the publicPath query to the file-loader

loader: "file?publicPath=../&name=./fonts/[hash].[ext]"

This will emit the files in fonts/* and but the publicPath will be .././fonts/** in your css file..

Maybe it helps some one..

Thanks for the tip! It would be great if this option was documented in the README.

Closing since the question has been answered. Feel free to add this to the readme with a PR.

ps: the param to the file-loader is publicPath - beware cut and paste of pubicPath from above

@dropfen , publicPath QueryString, best tip ever. Thanks!

we can also set the publicPath to an absolute path, so the assets can be accessed by all css

that sneaky publicPath=../ 😄