Source map support about tools HOT 25 OPEN

Please stop spamming my notification feed with +1 posts, use an emoticon reaction to signal your support and the star button to track it.

from tools.

related in a stackoverflow: http://stackoverflow.com/questions/34921477/how-to-implement-error-tracking-in-a-polymer

related in polybuild: googlearchive/polybuild#26

from tools.

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.

from tools.

Same for CSS too I guess.

from tools.

Would it be fair to say that if you placed your JS in external files that source maps would then be quite handy?

from tools.

+1 to this feature request

from tools.

+1

from tools.

+1

from tools.

+1 for feature request

from tools.

+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

from tools.

+¹

from tools.

+1 tracking bugs in production is a PITA without sourcemaps.

from tools.

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 ....

from tools.

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.

from tools.

@indolering are you combining vulcanize with any html/css minifiers? they can often cause subtle bugs

from tools.

@robdodson No, but I ran into a bug in Polybuild's CSS minifier too.

from tools.

In Polymer Starter Kit we had issues with polybuild and switched back to using Vuclanize by itself. Have you tried that?

from tools.

I combine only babel 5.x and than vulcanize together

from tools.

@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.

from tools.

+1

from tools.

+1

from tools.

+1

from tools.

+1

from tools.

+1

from tools.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from tools.