[wasm] introduce typescript modules

[pavelsavara]

Goals

Introduce typescript and break up the code to multiple, better encapsulated modules.

• use EMSDK nodejs for the build
• use rollup.js to produce ES6 IFFE because emscripten doesn't know how to consume ES6 modules on input.
• the ts output file runtime.iffe.js is compiled with emcc and AOT as --pre-js
• package.json references explicit versions of dev-time only dependencies. They are not necessary on link time.
• dependencies are resolved with npm ci in CI pipeline to make sure we get exactly same version as in lock file.
• we also run npm audit in CI so that we are sure we don't have new security issue in the CI.
• we have small rollup plugin which checks sha256 hash of the output and doesn't overwrite it if it's the same. So that incremental build/link is not broken.
• ignore_pdb_load_errors is now Module.config option

Non-goals

• just library_mono.js , the rest will be in follow up PRs
• functional changes
• later: lint, renames, more cleanup
• API change toward embedders like Blazor
• sourcemaps

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	pavelsavara
Assignees:	-
Labels:	arch-wasm
Milestone:	7.0.0

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[am11]

Would this make it possible to make WasmEnableES6 default to true with this change?

runtime/src/mono/wasm/wasm.proj

Line 10 in 4d41173

<WasmEnableES6 Condition="'$(WasmEnableES6)' == ''">false</WasmEnableES6>

WasmEnableES6 results in importable ES6 module for dotnet in deno environment. It's also compatible in browser (since WASM and ES6 are mutually supported everywhere).

[pavelsavara]

Would this make it possible to make WasmEnableES6 default to true with this change?

runtime/src/mono/wasm/wasm.proj

Line 10 in 4d41173

<WasmEnableES6 Condition="'$(WasmEnableES6)' == ''">false</WasmEnableES6>

WasmEnableES6 results in importable ES6 module for dotnet in deno environment. It's also compatible in browser (since WASM and ES6 are mutually supported everywhere).

I would love to, but I need to work thru all the consequences. Our unit test infrastructure and also the way how external projects like ASP.NET/Blazor consume us. So most likely it would not be in this PR.

But it's on my wish list too.

[pavelsavara]

OSX failure is unrelated timeout.

[pavelsavara]

@radical I introduced new file to AOT inputs. I don't know how it would impact VS/workloads. We will probably remove or rename all the other .js files too in next PR. Would something break in the meantime ?

[radical]

cc @Thays to try this with the debugger tests.