[browser] Is it possible to embed "js-module-native" and "js-module-runtime" JS modules?

[elringus]

In .NET 7 it was possible to run browser-wasm app with embedded assets:

import { dotnet } from './dotnet.js'

const config = {
    "mainAssemblyName": "Test.dll",
    "assemblyRootFolder": "managed",
    "assets": [
        {
            "behavior": "assembly",
            "buffer": ....,
            "name": "System.Runtime.dll"
        },
        {
            "behavior": "assembly",
            "buffer": ....,
            "name": "Test.dll"
        },
        {
            "behavior": "dotnetwasm",
            "buffer": ....,
            "name": "dotnet.wasm"
        }
    ]
};
dotnet.moduleConfig.configSrc = null; // required to force it not try to load config file.
const { getAssemblyExports, setModuleImports } = await dotnet.withConfig(config).create();

But .NET 8 now requires specifying js-module-native and js-module-runtime JS files. Is it somehow possible to workaround this, so that we can still bundle the whole stuff into a single JS file?

[maraf]

Resolved in #90392, right?

[elringus]

Confirmed this is working. Though I'm bit worried that dotnet.js, dotnet.runtime.js and dotnet.native.js seem to contain

import "process"
import "module"

— at least rollup complains about that on build. I've marked them as globals for now to mute the warnings, but this could cause issues when compiling for restricted environments. It would probably be better to access them conditionally via global context instead of importing (if possible).

Below is the msbuild config I've used to compile everything into single js file (in case someone finds this looking for a similar feature):

<Target Name="BundleJS" AfterTargets="_AfterWasmBuildApp">
    <Exec Command="npm install" WorkingDirectory="$(WasmAppDir)/"/>
    <Exec Command="npm version $(Version)" WorkingDirectory="$(WasmAppDir)/"/>
    <Exec Command="npm run build" WorkingDirectory="$(WasmAppDir)/"/>
</Target>

package.json:

{
    "name": "foo-lib",
    "version": "0.0.0",
    "module": "foo-lib.js",
    "scripts": {
        "build": "rollup foo-main.js -o foo-lib.js -f es -g process,module"
    },
    "devDependencies": {
        "rollup": "^3.28.0"
    }
}

foo-main.js:

import * as runtimeModule from "./_framework/dotnet.runtime.js";
import * as nativeModule from "./_framework/dotnet.native.js";
import { dotnet } from "./_framework/dotnet.js";

export async function boot() {
    /** @type {import("dotnet").MonoConfig & { assets: import("dotnet").AssetEntry[] }} */
    const config = {
        mainAssemblyName: "Foo.dll",
        assets: [
            {
                name: "dotnet.runtime.js",
                moduleExports: runtimeModule,
                behavior: "js-module-runtime"
            },
            {
                name: "dotnet.native.js",
                moduleExports: nativeModule,
                behavior: "js-module-native"
            },
            {
                name: "dotnet.native.wasm",
                buffer: await fetchBin("dotnet.native.wasm"),
                behavior: "dotnetwasm"
            },
            {
                name: "System.Private.CoreLib.wasm",
                buffer: await fetchBin("System.Private.CoreLib.wasm"),
                behavior: "assembly"
            },
            {
                name: "Foo.wasm",
                buffer: await fetchBin("JSInteropTest.wasm"),
                behavior: "assembly"
            }
        ]
    };

    const runtime = await dotnet.withConfig(config).create();
    runtime.setModuleImports("foo", { ... });
    await dotnet.run();
    return await runtime.getAssemblyExports(config.mainAssemblyName);
}

async function fetchBin(name) {
    // alternatively, binaries can be converted to base64 and embedded to the JS.
    return new Uint8Array(await (await fetch(`./_framework/${name}`)).arrayBuffer());
}

[Kuinox]

Thanks a lot, I'm hitting the same problem when upgrading the draco web playground and your sample helps a lot!