[browser][MT] support for NodeJS

[elringus]

With <WasmEnableThreads>true</WasmEnableThreads> generated dotnet.js has assert to only be used in browser environment. When imported (w/o actually creating the runtime), following error is thrown:

This build of dotnet is multi-threaded, it doesn't support shell environments like V8 or NodeJS.

This breaks unit testing in node when the dotnet APIs are mocked and the runtime is not initalized, but still has to be imported. After removing the assertion unit testing in node works fine.

Is it possible to remove the assertion or move it to the runtime creation function?

[ghost]

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

Issue Details

---

With <WasmEnableThreads>true</WasmEnableThreads> generated dotnet.js has assert to only be used in browser environment. When imported (w/o actually creating the runtime), following error is thrown:

This build of dotnet is multi-threaded, it doesn't support shell environments like V8 or NodeJS.

This breaks unit testing in node when the dotnet APIs are mocked and the runtime is not initalized, but still has to be imported. After removing the assertion unit testing in node works fine.

Is it possible to remove the assertion or move it to the runtime creation function?

Author:	Elringus
Assignees:	-
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript, needs-area-label, os-browser
Milestone:	-

[pavelsavara]

This is by design. What are the use cases which you need to address
Oh, I miss-read the description

[pavelsavara]

yeah, MT on NodeJS is not even close to ready. Why are you importing the module when you mock it anyway ?

[elringus]

I mock individual bindings, but not the whole module. Here is an example: https://github.com/Elringus/DotNetJS/blob/feat/revamp/Samples/App/test/computer.test.tsx (backend is the dotnet module).

[pavelsavara]

This needs emscripten bump to 3.1.52

[lewing]

cc @radekdoulik