Description
perhaps just look for existing fileName.js.map file, then use that as the input source map to the next stage of the transform.
Prefer using fileName.js.map, with .js extension since it is conceivable down the road that there is a fileName.html.map, fileName.js.map. I suppose as a stopgap, also look for fileName.map assuming that it is the map to go into JS.
While that would work for "whole directory" optimizations, single file optimizations, where for example, maybe just out= is used (or in the browser out = function (){}), then it would be nice to pass the maps through the code flow without having to touch disk.
In requirejs/require-cs#42, @guybedford suggested perhaps something passed to load.fromText as a way to do this.
The "use existing .map" file change may be easy to support for 2.1.7, not sure about the other path yet.