[stephan-dum]

What is the current behavior?

1. the source map sources paths are pointing to non existing files (missing ../../)
2. the dist files contain multiple source map references where the first one is non existing

GitHub Issue Number: #6959

What is the new behavior?

1. source map paths are correct

by adding dir to all RollupOutputOptions the sourcemap.sources property is correct. This requires to loop all possible outputTargets (similar to collection and customElements output targets)

the dir for system output targets was pointing to esmDir which uses now systemDir instead.

es5 builds now are in there own directory using esmEs5Dir

2. only one referenced source map per file

es5 ts.transpileModule added a source map reference for module.ts which is remove now.

minify options format.comments is now applied to all targets. There seams to be an inconsistency with sourcemap reference comment when this option is set it will not remove the reference comment. This means there is no need anymore for the getSourceMappingUrlForEndOfFile function so its completly removed.

lazyBundleIdPlugin function is also removed to keep naming of source map reference and the actual source file in sync. This should be already covered by template strings:

chunkFileNames: config.hashFileNames ? 'p-[hash].js' : '[name]-[hash].js',
assetFileNames: config.hashFileNames ? 'p-[hash][extname]' : '[name]-[hash][extname]',

Does this introduce a breaking change?

• Yes
• No

Testing

All unit tests are passing
Added new e2e test cases to prevent it in the future