-
Notifications
You must be signed in to change notification settings - Fork 19
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
Make the sourcemap available #6
Comments
Is this a symptom where the bundle builds a compiled correctly css file in var/sass/* but asset-mapper is still just serving a temp file that is an exact replica of the original scss? That is what i am getting, not sure what i am missing. As a validation that the SASS build side is working properly, i added an exclude on the asset-mapper config.yaml to ignore scss files, then added an path to var/sass/. and changed the link in the template to app.output.css and it does work correctly. So its something with how the bundle is supposed to override the default scss rendering. |
This PR was merged into the main branch. Discussion ---------- Using realpath everywhere for consistent comparison #6 (comment) Commits ------- 78955f5 using realpath everywhere for consistent comparison
Confirming that 2.2 resolved the issue i was having. Thanks! Related to your note, i have two questions, |
When the package builds, a
.map
file is output. But, we're not currently making it available.Another option is to pass
--embed-source-map
and embed it directly in the CSS file (indev
mode only).The text was updated successfully, but these errors were encountered: