-
Notifications
You must be signed in to change notification settings - Fork 12k
WASM support regression when switching to the esbuild builder #26826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Loading wasm using ES module imports is non-standard: https://developer.mozilla.org/en-US/docs/WebAssembly/Loading_and_running#what_are_the_options Angular 17.1 (to be released) allows to specify a loader type for any extension, which should help make this work. |
Oh, wow thanks. I've been using Wasm for years and thought that it's been standardized for a while. The ESM integration repo for Wasm is over 7 years old but not ready yet it seems. (currently at phase 2) |
This is known, please see https://angular.dev/tools/cli/build-system-migration#unimplemented-options-and-behavior and #25102 |
For reference, the feature for loader types was implemented in #26371. It still requires to instantiate the module as described in the MDN link so it's I don't think there's a config yet to retrieve support as with Webpack. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug?
compiler
Is this a regression?
Yes
Description
I am updating my project from
"builder": "@angular-devkit/build-angular:browser"
to"builder": "@angular-devkit/build-angular:application",
since it's the recommended builder.Unfortunately, I now get an error related to a WASM module in one of my dependencies. No Wasm support is a blocker for me to update.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: