Introduced a new property mapOpts.inMap to function generateSourcemap() in generate-sourcemap.js. This property may contain a sourcemap that has been read through options.map in function ngAnnotate().
For now one can access this only using the library API. I have deliberately not touched the CLI portion as I think that the library author is in a better position to make that change.
My suggestion would be to allow --inMapFile for the command line which can take the path from which the source map can be read into config.map.inMap. For the library user, it will be their responsibility to read the file and map it to config.map.inMap. Eventually, the code in function generateSourcemap() can check if it is a string or an object to use JSON or Object source map transformation at the level of convert-source-map library.
Introduced a new property
mapOpts.inMap
tofunction generateSourcemap()
ingenerate-sourcemap.js
. This property may contain a sourcemap that has been read throughoptions.map
infunction ngAnnotate()
.For now one can access this only using the library API. I have deliberately not touched the CLI portion as I think that the library author is in a better position to make that change.
My suggestion would be to allow
--inMapFile
for the command line which can take the path from which the source map can be read intoconfig.map.inMap
. For the library user, it will be their responsibility to read the file and map it toconfig.map.inMap
. Eventually, the code infunction generateSourcemap()
can check if it is a string or an object to use JSON or Object source map transformation at the level of convert-source-map library.Please be gentle, this is my first PR :)