You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there. I'm not sure if this is a bug with this plug-in or something with Webpack itself, or one of the other loaders (MiniCssExtractPlugin.loader, css-loader, postcss-loader, or sass-loader), but when I build on my Windows laptop, the paths that are altered in the resulting CSS use backslashes rather than slashes, which results in invalid URLs.
Can you provide reproducible test repo (github?) with example of code, because it is hard to say where is bug without additional infromation, thank you
Bug report
Hi there. I'm not sure if this is a bug with this plug-in or something with Webpack itself, or one of the other loaders (
MiniCssExtractPlugin.loader
,css-loader
,postcss-loader
, orsass-loader
), but when I build on my Windows laptop, the paths that are altered in the resulting CSS use backslashes rather than slashes, which results in invalid URLs.The workaround I'm using right now is with:
But that shouldn't be necessary.
Actual Behavior
URLs altered end up like the second one (note the backslashes):
Expected Behavior
URLs should all use slashes rather than backslashes like so:
How Do We Reproduce?
I'm compiling from Sass:
I've attached my webpack.config.js in case I'm doing something wrong there.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationThe text was updated successfully, but these errors were encountered: