Skip to content

[wasm] Design application startup, template, configuration #70892

Closed

Description

TODO

  • Adopt blazor.boot.json like format, instead of mono-config.json
  • Separate assets/manifest from application config from current run arguments
  • Unify the templates and it's runArgs.json
  • PATH-like DLL resolution for nodeJS, (and WASI?)
  • runtimeconfig.json/.bin and launchsettings
  • remove features like proxyConsoleMethod from template, or integrate them with runtime
  • Incremental updates
  • Try to load assemblies to VFS (instead of WASM memory) and let runtime load them from there
  • [wasm][nodejs] implement synchronous DLL loading #79981 - on NodeJS/V8 let runtime load assemblies on the fly from local filesystem without extra boot config
  • Experiment with serializing initial wasm memory instead of loading dlls
  • Experiment with inlined mono-config (faster startup, in-place URLs of all assets)
  • [browser] Split dotnet.js and introduce loader + emscripten modules #85045
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions