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
{{ message }}
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
Now that we are sending outPath to downstream (so it handles sourceMaps related path correctly), shouldn't we make it practice to resolve image URLs w.r.t. generated CSS file location (so implementers don't have to post-process these using separate AST, like this)?
According to https://github.com/sass/node-sass#imagepath, whatever path is set to imagePath, it will be prepended to output for
image-url(..)
, which is;url(..)
.Now that we are sending
outPath
to downstream (so it handles sourceMaps related path correctly), shouldn't we make it practice to resolve image URLs w.r.t. generated CSS file location (so implementers don't have to post-process these using separate AST, like this)?Reproduction steps: less/less.js#2084 (comment) (just replace less with scss).
@andrew, @mgreter,
The text was updated successfully, but these errors were encountered: