You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And have uglifyjs compose all the input files' source maps together.
The source-map.content option allows for inline, which will correctly compose files like file3.js. The option also also allows for giving the actual source map JSON via the CLI, which I believe only works for a single input file.
I am proposing (and am currently working on) an option for source-map.content called auto, which will attempt to resolve source maps in this way:
If sourceMappingURL is specified, decode the base64 if the source map is inline. If the source mapping url is a resource location (either a file on disk or an HTTP asset), fetch it.
If there is no sourceMappingURL, and the input file name is file.js, look for the source map on disk at file.js.map and file.map
The text was updated successfully, but these errors were encountered:
Related to #3058
Currently, there is no way to provide inputs such as this:
file1.js
file2.js
file3.js
And have uglifyjs compose all the input files' source maps together.
The
source-map.content
option allows forinline
, which will correctly compose files likefile3.js
. The option also also allows for giving the actual source map JSON via the CLI, which I believe only works for a single input file.I am proposing (and am currently working on) an option for
source-map.content
calledauto
, which will attempt to resolve source maps in this way:sourceMappingURL
is specified, decode the base64 if the source map is inline. If the source mapping url is a resource location (either a file on disk or an HTTP asset), fetch it.sourceMappingURL
, and the input file name isfile.js
, look for the source map on disk atfile.js.map
andfile.map
The text was updated successfully, but these errors were encountered: