[TIMOB-12869] Ensure all AST modifications are pipelined resulting in a single source map file
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Low |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | CLI |
| Labels | cb-tooling |
| Reporter | Ingo Muschenetz |
| Assignee | Chris Barber |
| Created | 2013-02-26T19:51:36.000+0000 |
| Updated | 2020-02-13T17:59:09.000+0000 |
Description
As part of the deployment process, we consider a simple, common case: an Alloy application that has been minified.
We need to make sure that the resulting source map packaged with the app includes the results of both sets of transformations--first those made by Alloy, and then those made by build process itself.
For reference, all source maps created with the [source-map format maintained by Mozilla](https://github.com/mozilla/source-map), which is in use by Uglify-js, can be "chained" together. By this I mean that a source map created by Alloy could then be used as an input parameter when attempting to create another source map on top of it. This would let you map the chain of files and transformations all the way back to the original files, regardless of the number of times additional source maps were created. The above link shows the mozilla library for handling source-map formatted source maps, and it is extremely simple to use. That library is only for JS, working in the browser and Node.js. There is a Java port as well, found here: https://code.google.com/p/closure-compiler/source/browse/#git%2Fsrc%2Fcom%2Fgoogle%2Fdebugging%2Fsourcemap
Downgrading priority as there is no current urgency for this.