-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Closed
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-System.Runtime.InteropServices.JavaScriptin-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is mergedos-browserBrowser variant of arch-wasmBrowser variant of arch-wasm
Milestone
Description
- Both parts of lazy loading definition requires to use assembly file name (including extension)
- With webcill an extension for assembly changes from
.dllto.wasm - Current behavior requires to change lazy loading definition when switching between webcil and non-webcil
- Ideally lazy loading definition should be without file extension
- Making both extensions work is a blocker, because JS part of the runtime doesn't currently know if webcil was used or not. We probably could check for file with user passed extension in assets and if not found, check for
.wasm
Metadata
Metadata
Assignees
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-System.Runtime.InteropServices.JavaScriptin-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is mergedos-browserBrowser variant of arch-wasmBrowser variant of arch-wasm