-
Notifications
You must be signed in to change notification settings - Fork 4
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
Source maps output #130
Comments
My library does nothing to the source map content. It only tells the embedded compiler to generate a source map and then passes the source map generated by the compiler back to you. The embedded protocol actually enforces the missing For the |
Gotcha. Well the absolute paths are easy enough to relativize post-hoc. Feel free to close this if you decide it is not an issue with the library. Thanks again! |
I'm not sure what to do about this, yet. On the one hand I completely understand that the current source maps (with absolute paths) are pretty useless. On the other hand, I don't know how to improve the situation. Neither the embedded compiler nor my host library have enough context to create better source maps. |
Apologies, I didn't want to open a whole other issue for this, but just wanted to stop by and say that there is now a Clojure |
Hi there,
I just recently tried to generate source maps via the embedded compiler and the source maps that are being generated are different than what you get from CLI dart-sass. The actual compiled css files are correct, the issue is just with the source maps.
With this embedded compile I'm getting something like:
Whereas dart-sass CLI produces something like:
Specifically, the output "file" is missing, but more importantly the paths are absolute, which will probably break. Does this seem right?
I based my usage on the tests in
SassCompilerTest.java
, basically I justsetGenerateSourceMaps
on the compiler, and that was it. Is there some other configuration that I'm missing, or some usage example I may have missed?Thanks for this great library!
The text was updated successfully, but these errors were encountered: