Backwards compatibility implementation for pre 1.3.0 link method.
The major interface change in 1.3.0 is that the linker (and not the
caller) determines the set of files to be written. As a consequence, the
post 1.3.0 API does not offer as much control over cross-file references
(i.e. source map links): it is based on patterns rather than simply
asking the caller to verbatim provide the URI to reference in each file.
To provide a backwards compatible interface, we do the following post-run
processing:
Match and copy the produced set of files (in the OutputDirectory) to
the files provided by the caller (in LinkerOutput).
Replace the pattern generated cross-file references with the ones
provided by the caller. This is necessary as a post-processing step,
because of the reduced flexibility of the 1.3.0 API: we cannot express
all legacy requests in the new API.
Backwards compatibility implementation for pre 1.3.0 link method.
The major interface change in 1.3.0 is that the linker (and not the caller) determines the set of files to be written. As a consequence, the post 1.3.0 API does not offer as much control over cross-file references (i.e. source map links): it is based on patterns rather than simply asking the caller to verbatim provide the URI to reference in each file.
To provide a backwards compatible interface, we do the following post-run processing:
(Since version 1.3.0) Part of legacy API.