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
{{ message }}
This repository has been archived by the owner on Sep 6, 2022. It is now read-only.
if the package works as I suppose it does, i.e., by first generating a spacebar file and then reusing Blaze's spacebar to JS generator.
But if the answer to both those interrogations are positive, then it would be awesome to:
write the intermediate spacebar file somewhere into the .meteor folder
generate a jade2spacebar.map source map file tracing the correspondence between the source jade file lines to the intermediate spacebar file lines
generate a spacebar2js.map source map file tracing the correspondence between the intermediate spacebar file lines to the web.browser/app.js file served to the browser (though that should probably belong as a feature request on the blazejs project rather than here)
reusing the two other maps above to generate a jade2js.map source map tracing the correspondence between the source jade file and the web.browser/app.js file served to the browser.
This would allow one to write extensions for IDEs such as WebStorm and VSCode allowing to put breakpoints in jade templates, which would greatly speed-up debugging of jade-meteor apps with beyond toyish trivial UI components.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am not sure whether:
But if the answer to both those interrogations are positive, then it would be awesome to:
This would allow one to write extensions for IDEs such as WebStorm and VSCode allowing to put breakpoints in jade templates, which would greatly speed-up debugging of jade-meteor apps with beyond toyish trivial UI components.
The text was updated successfully, but these errors were encountered: