These are chat archives for opal/opal

29th
Dec 2015
Mitch VanDuyn
@catmando
Dec 29 2015 18:18
We suddenly have a weird thing going in chrome debugger. Source mapping is turned off (and has been for a long time)
Now every single source line (like when it does a console log, hits a break point, whatever) is always the same line: jquery.contextMenu.min.js:1846 All of our JS files are there, but everything seems to map back to this same line.
Mitch VanDuyn
@catmando
Dec 29 2015 18:24
So for example if I open up a file in the chrome source debugger (say application.js) and try to set a break point at some line. It immediately opens up jquery.contextMenu.min.js and sets the break point at 1846!
Hopefully somebody else has seen this?
Mitch VanDuyn
@catmando
Dec 29 2015 18:50
Fixed it... jquery.contextMenu.min.js has this line requesting a sourcemap, and that was causing the headache
Jamie Gaskins
@jgaskins
Dec 29 2015 23:56
I've been looking at how Ember and React have separate builds for dev and production. The dev build has debug info and warnings that the production build doesn't have. Is it possible to do the same with Opal? I'd like to be able to compile development warnings into Clearwater, but not in a production build.