Monday, December 15, 2014

Re: source maps unreliable in 2.7.0

I am not aware of any way to tell Chrome to try requesting source maps again beside reloading the page. Honestly I would never use Chrome Canary for development since you never know if Chrome misbehaves or not.

I am fine with Chrome 39 and Chrome 40 beta. Never had a problem with source maps not being downloaded.

Also I don't really had a problem with debugging. You can see the current scopes variable values in Chrome, set watch expressions and conditional breakpoints. This also works within IntelliJ (and probably in Eclipse using SDBG), although you always must keep in mind that you are debugging JavaScript. So conditional breakpoints need JavaScript expressions and variable names are JavaScript variable names since they are not mapped using source maps (the source map spec does not define this yet).

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment