Source map support about broccoli-coffee HOT 5 OPEN

Would it really be that difficult to support? It could be exposed by passing all options along instead of just the bare option.

from broccoli-coffee.

The big blocker is that we don't currently support multi-file input and output in the broccoli-filter base class, which is responsible for caching (smart rebuilding).

Source maps are fairly complex in general, but maybe it's not terribly hard to add support. Here's a checklist:

• Source map support should just work by default and not require manual configuration. E.g. we can put it behind a boolean flag (which we can default to true once it's stable).
• References from .js to .js.map files need to work
• References from .js.map to .coffee sources need to work - either by copying the sources into the output tree, or by inlining them into the sourcesContent source map property
• Chained transformation should work as well, i.e. having an input source map as well as an output source map. Again, when an input source map is present, things should just work and not require manual configuration.

from broccoli-coffee.

Regardless of the difficulty, my sense of things from watching the attention shift around among various build/task running tools is that users will expect a plug-in supports "X" to support generally most of the feature set of X.

from broccoli-coffee.

This might be adequately implemented by #9.

from broccoli-coffee.

Version 1.11.0 of CoffeeScript contains some changes that might be relevant to this:

Added the -M, --inline-map flag to the compiler, allowing you embed the source map directly into the output JavaScript, rather than as a separate file.

http://coffeescript.org/#changelog

from broccoli-coffee.