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
If this is a feature request, what is motivation or use case for changing the behavior?
not required
Please mention other relevant information such as your webpack version, Node.js version and Operating System.
not required
Why it is happens: we use from - "/css-loader!" + options.from and when postcss build source map he use this as the dirname of the path to the SourceMap to be applied (https://github.com/postcss/postcss/blob/master/lib/map-generator.es6#L107). It is output invalid sources location (all sources interpreted as relative to from, but source can be not relative to from).
Do you want to request a feature or report a bug?
maybe bug
What is the current behavior?
Invalid
sources
in map then your usesass-loader
andcss-loader
. More information inside issue belowIf the current behavior is a bug, please provide the steps to reproduce.
Repo: webpack-contrib/sass-loader#484 (comment)
What is the expected behavior?
sources
in map should be valid location.If this is a feature request, what is motivation or use case for changing the behavior?
not required
Please mention other relevant information such as your webpack version, Node.js version and Operating System.
not required
Why it is happens: we use
from
-"/css-loader!" + options.from
and whenpostcss
build source map he use this asthe dirname of the path to the SourceMap to be applied
(https://github.com/postcss/postcss/blob/master/lib/map-generator.es6#L107). It is output invalid sources location (all sources interpreted as relative tofrom
, but source can be not relative tofrom
).Workaround (before https://github.com/webpack-contrib/css-loader/blob/master/lib/processCss.js#L196):
But I'm not sure.
The text was updated successfully, but these errors were encountered: