-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Absolute instead of relative paths in sourcemap with dart-sass #299
Comments
Is this repo still maintained? I don't think it can be answered in one of the Sass-parser repo's since it's the specific implementation of grunt-sass that seems to cause this issue. |
I think that
I haven't yet figured out if there's a way around this. |
Not sure there's much to be done here as node-sass is basically telling people to use dart-sass for continued support and you're right that it looks like they are forcing stdout to use absolute urls. Just reemphasizing that this is sad since the default for |
I just migrated to dart-sass and discovered all sourcemap paths are now absolute instead of relative. Passing |
We're also having this issue, would love to know if there has been any movement. |
What about this approach? - using sourceMapContents to make bigger but more dependable map files? Is that possible here, or still not possible because we're using the API and not command line? |
This feels like a totally crazy hack approach that should not be necessary, but for now, I'm using grunt-string-replace to get this done:
|
I have the following example config in Gruntfile.js:
The output of the two mapping files is:
test.dartcss.css.map
test.nodecss.css.map:
You can see that
test.dartcss.css.map
contains absolute paths instead of relative paths to the sources. Thesass
cli command has the following property to control this:How can we tell grunt-sass/dart-sass to use relative paths?
The text was updated successfully, but these errors were encountered: