alltom
commented
10 years ago It does optionally generate source maps, but it's really slow and turned off by default. It's really slow! Theseus makes a lot of edits so the maps are large.
I even forked falafel just to make it work. :) But stepping through source-mapped code in Chrome was so buggy at the time, and it made pages take so much longer to load, that I just turned it off.
Generation of source maps is turned back on by passing { source_map: true } to traceFilter. You can hack that in yourself, but for something I can release, a little work would be needed in each of the three projects:
- [ ] fondue: Pass
source_map: true/falsehere by getting from the options provided to instrument(). - [ ] node-theseus: instrument is called from here. A command-line argument should be created for it here.
- [ ] Theseus (the Brackets extension): instrument is called from here (JavaScript files) and here (embedded script tags). An argument for it should be added to the getServer command, which is called from here. The parameter for whether to generate source maps should probably provided from a preference that works like the Static/Proxy options in the File menu (which is all handled by main.js).
Bonus:
- [ ] Make it tolerable with caching. Checksum the input files and store the instrumented versions on disk.
If anyone wants to take any part of this on, let me know! The node-theseus case is pretty simple. As with all issues, this is going on my to-do list but it might take me a little while to get to it. :)
OKNoah
Theseus rewrites your JavaScript Source, but it doesn't generate sourcemaps.
Hence if you install the the Console Tools plugin to help debugging issues in the code for example, the line numbers are completely screwed.
Also when you open the Developer Tools in Google Chrome you see the unreadable instrumented code, instead of the code you wrote.