search

HoriSun / closure-compiler

Automatically exported from code.google.com/p/closure-compiler
0 stars 0 forks source link

Output source map does not use input source maps #1296

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Build https://gist.github.com/evanw/10008901
2. Look at the generated source map

What is the expected output? What do you see instead?

I expected output source map to be a transformed version of the input source 
map (the input file contains the "//# sourceMappingURL" pragma at the bottom). 
Instead, the input source map is ignored.

The transformation should at least preserve the original file names and 
line/column mappings, but it would also be very helpful to have an option for 
the sourcesContent field to be carried over and updated. I'm using closure 
compiler to optimize the output of a custom compile-to-js language as you can 
tell from the input source map.

What version of the product are you using? On what operating system?

Version: v20140303
Built on: 2014/03/04 10:53
Mac OS X 10.9.2

Please provide any additional information below.

Original issue reported on code.google.com by evan....@gmail.com on 6 Apr 2014 at 5:28

GoogleCodeExporter commented 9 years ago 
This is useful for other compilers whose priority isn't speed nor compression 
to use the closure compiler. Basically means a composition of source-maps.

Original comment by lgand...@gmail.com on 16 Apr 2014 at 8:25

GoogleCodeExporter commented 9 years ago 
I would also like this feature, i've also noticed that the source map "source" 
uses an absolute path to the file not not realtive to the JS file which means i 
need to edit both files manually and can't include this in a build script.

Original comment by pig...@rubberpigeon.com on 17 Apr 2014 at 4:59

GoogleCodeExporter commented 9 years ago 
also https://code.google.com/p/closure-compiler/issues/detail?id=941 is the 
same issue, and no you can't get around this using --output_wrapper flag.

Original comment by pig...@rubberpigeon.com on 17 Apr 2014 at 5:00

GoogleCodeExporter commented 9 years ago 
Issue tracking has been migrated to github. Please make any further comments on 
this issue through https://github.com/google/closure-compiler/issues

Original comment by blic...@google.com on 1 May 2014 at 6:31

GoogleCodeExporter commented 9 years ago

Original comment by blic...@google.com on 1 May 2014 at 6:34