--dev incompatible inside chrome extensions

[timoxley]

Just FYI, if you try to use files built with component build --dev in a chrome extension, you'll get an error like the following:

Uncaught Error: Code generation from strings disallowed for this context

Workaround for now is to remove the --dev, and deal with the lack of sourcemaps etc.

This is probably more an issue with component-builder

[tj]

oh lame :(

[edmellum]

This could be fixed by using sourcemap instead of SourceURL since sourcemap doesn't require an eval. However sourcemaps aren't really supported that well in current debug tools so variables aren't mapped back properly.

[tj]

sourcemaps are huge PITA too, I guess we could have a --no-source-url flag or something :s haha

[edmellum]

Having source URLs behind a flag is nice for IE debugging too. Or maybe someone should make a builder that spits out <script> tags or something.

[tj]

a lot more work for no gain really, if you're using coffeescript or something sure, but I sure wouldn't bother with js

[tj]

I guess, I dont find it to be a problem without

[bestander]

+1 for debugging in production, especially with all the line numbers preserved it helps to send bug reports for 3rd party components

[gjohnson]

Related: http://developer.chrome.com/extensions/sandboxingEval.html

[jonathanong]

closing this and moving discussion to componentjs/builder2.js#26

if you guys know a really simple library that easily makes source maps from just concatenating stuff, let me know!