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-map support #135
Comments
Can we close this as a duplicate of #88? |
Well in my opinion having source-maps is even better than line-numbers. Maybe I should have made it as a separate issue.. |
I changed the title and added the 3.3 label as it's a feature parity issue. |
Having source maps will definitively make debugging easier for example by using it in Chrome developer tools window |
I've forked this project and added the line number feature into the develop branch: update June 2015: |
Branch:
|
(p.s. --line-numbers and --debug-info are available in the latest version of scssphp) |
@robocoder Any update on source maps? Or do you maybe know about any Chrome plugin that would work with --line-numbers? Thanks a lot! |
@acasar Support for sourcemaps is a work-in-progress being juggled with other issues (eg selectors and scope). Sorry, I don't know of any Chrome plugins that support --line-numbers. |
+1 for this |
Please please add sourcemaps - it is impossible to do live debug (remote) without it. |
@robocoder Could you share your current code for source maps' generation? I desperately need them, maybe I could pick up where you left and finish that feature? |
@wojtas: there's not much here: https://github.com/leafo/scssphp/tree/wip/source-maps |
+1 for source maps |
1 similar comment
+1 for source maps |
If anyone is interested - in my project I managed to quite easily extract line number comments to a real source map using this package: https://github.com/koala-framework/sourcemaps @robocoder Maybe if we add it as a dependency it would be much easier to implement source maps natively? |
Feel free to submit a PR. |
Removed one TODO from the README file: Checked it is not currently possible to do source maps with leafo/scssphp. More details: leafo/scssphp#135
+1 for source-maps. Has been over a year since it being a WIP. Would love to see it eventuate, but not sure if it's likely any time soon? |
Here is my gist: The code extends the Leafo\ScssPhp\Server. The most important methods for generating maps is |
+1 for source maps |
See #541 : inline sourceMap generation. I did not add the command line switches nor detached source map, but the hardest part is done. And it works really well with https://github.com/NicolaF/autoprefixer-php. (See vladkens/autoprefixer-php#13) |
@NicolaF, i'll go ahead and try that commit to see how it works. Any special config or it just "works"? |
@riverofjanuary It just works ;-)
The option names are a bit misleading, but I kepts the names from oyejorge/less.php, for those of us who are transitioning to bootstrap 4 and used oyejorge/less.php with the less version of bootstrap 3. |
Thanks. I see I cant actually pull that SHA because it hasn't been committed, but I'll wait to see what the dev does. |
See #135: add inline sourceMaps support
There are currently two ways how you can debug sass quite easily:
As far as I know both of the above features aren't implemented in scssphp, but it would be a great addition! Now it's really hard to track where that rule was written.
The text was updated successfully, but these errors were encountered: