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
I made a little tool (gen-pug-source-map), based on your idea for generating source maps for Pug v2.x
My implementation solves some issues present in yours:
Each source file (included and extends) are readed from the file system multiple times, gen-pug-source-map does not read from the file system.
Absolute filenames in the property sources can hinder remote debugging.
In some cases, line numbering is shifted
Also, you can get the compiled code from gen-pug-source-map with inline templates removed.
If you want test it, please clone my repo, run npm i && npm t and go to http://sokra.github.io/source-map-visualization/#custom, click "Custom..." and upload test/output/app1.js, then load test/output/app1.map.js and try.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi @sidorares ,
I made a little tool (gen-pug-source-map), based on your idea for generating source maps for Pug v2.x
My implementation solves some issues present in yours:
included
andextends
) are readed from the file system multiple times, gen-pug-source-map does not read from the file system.sources
can hinder remote debugging.Also, you can get the compiled code from gen-pug-source-map with inline templates removed.
If you want test it, please clone my repo, run
npm i && npm t
and go to http://sokra.github.io/source-map-visualization/#custom, click "Custom..." and uploadtest/output/app1.js
, then loadtest/output/app1.map.js
and try.Thanks.
The text was updated successfully, but these errors were encountered: