Are there any plans to support source maps in Vulcanize? Like any other transformation tool, it'd be really valuable to be able to trace code back to the original source.
I'm not aware of any other tool creating source maps for HTML yet (as opposed to the usual CSS/JS), so the spec might need some adapting in terms of how the source map is referenced from a comment at the end of the generated source file.
theefer
All 24 comments
I'll keep this in mind with the refactor I'm doing in #13
I don't believe any browser is capable of understanding anything like an HTML sourcemap at the moment, but I'll evaluate as I go.
dfreedm
on 24 Feb 2014
Would it be fair to say that if you placed your JS in external files that source maps would then be quite handy?
pope
on 18 Aug 2014
Same for CSS too I guess.
theefer
on 18 Aug 2014
+1 to this feature request
williamcodes
on 3 Mar 2015
+1
phreaknation
on 9 Jun 2015
+1
zeitiger
on 27 Aug 2015
+1 for feature request
NamTThai
on 1 Sep 2015
+1 what's the status on this? would it likely entail a lot of work?
for things like Chrome's downloads or settings page, we'd probably want some way of reversing a trace back to original code line number as we get a lot of bugs in the wild that are hard to reproduce ourselves
danbeam
on 21 Oct 2015
+鹿
vinzdef
on 22 Oct 2015
+1 tracking bugs in production is a PITA without sourcemaps.
indolering
on 18 Dec 2015
I don't believe any browser is capable of understanding anything like an HTML sourcemap at the moment, but I'll evaluate as I go.
@azakus This is a datapoint of one, but the size of my elements are 10:1 JS:HTML/CSS. When used in conjunction with CSP ....
indolering
on 19 Dec 2015
I've officially run into two bugs in production that I can't reproduce without running it through Vulcanize/Polybuild. The lack of source maps makes Polymer unsuitable for production use and this ticket should at least be prioritized.
indolering
on 14 Jan 2016
@indolering are you combining vulcanize with any html/css minifiers? they can often cause subtle bugs
robdodson
on 14 Jan 2016
@robdodson No, but I ran into a bug in Polybuild's CSS minifier too.
indolering
on 18 Jan 2016
In Polymer Starter Kit we had issues with polybuild and switched back to using Vuclanize by itself. Have you tried that?
robdodson
on 19 Jan 2016
I combine only babel 5.x and than vulcanize together
zeitiger
on 19 Jan 2016
@robdodson Turning CSP back on fixed it, I had manually disabled it. I'm just afraid that something is going to break in the future and I will be unable to troubleshoot it properly. I can't risk releasing something into production that I might have to pull because I can't troubleshoot what's wrong with the vulcanize or the minifier.
indolering
on 20 Jan 2016
related in a stackoverflow: http://stackoverflow.com/questions/34921477/how-to-implement-error-tracking-in-a-polymer
related in polybuild: https://github.com/PolymerLabs/polybuild/issues/26
Qvatra
on 21 Jan 2016
+1
difosfor
on 17 Feb 2016
+1
LuisTJap
on 7 Jun 2016
+1
kito99
on 20 Jul 2016
+1
ronnyroeller
on 21 Jul 2016
+1
maxiplay
on 31 Aug 2016
Please stop spamming my notification feed with +1 posts, use an emoticon reaction to signal your support and the star button to track it.
indolering
on 2 Sep 2016
Related issues
rictic
路
3Comments
ronnyroeller
路
4Comments
priyabrat1801
路
3Comments
marcushellberg
路
3Comments
davidmaxwaterman
路
4Comments
Most helpful comment
Please stop spamming my notification feed with +1 posts, use an emoticon reaction to signal your support and the star button to track it.