fix: source maps for ES modules have wrong offsets after conversion to AMD (#1214)

[nenadvicentic]

Fixes issue with ES module source maps, after conversion to AMD. Described here #1214.

[3cp]

Thx!

[3cp]

@bigpon pls release a patch version. Thx!

[bigopon]

3.0.6 has been published, thanks @nenadvicentic @3cp 🙏

[nenadvicentic]

@bigopon @3cp Thank you both!

I just updated one of my projects to CLI 3.0.6. Works like charm.!You can see in the screenshot:

Only, I noticed another small thing. When I disable cache in aurelia.json -> build.options.cache: false I get new, correct source map (see screenshot). However, when I switch it back to default value "dev & stage", I, again, get previous, broken source map. Source file did not change, only tsconfig.json, so it makes sense to some extent. Can you remember from the top of your head - how long is cache valid for the project?

UPDATE:
Ah, I get it now. Source map has to be added to the cache too:

cli/lib/build/bundled-source.js

Lines 278 to 284 in 97d70ab

	// write cache
	if (useCache && hash) {
	Utils.setCache(hash, {
	deps: deps,
	contents: this.contents
	});
	}

And treated in a similar way as content is treated:

cli/lib/build/bundled-source.js

Lines 20 to 22 in 97d70ab

	get sourceMap() {
	return this.file.sourceMap;
	}

cli/lib/build/bundled-source.js

Lines 32 to 36 in 97d70ab

	get contents() {
	return this._contents === null
	? (this._contents = this.file.contents.toString())
	: this._contents;
	}

I can adopt this in a new pull request.