Skip to content

Conversation

alexcrichton
Copy link
Contributor

Currently the import object constructed for the --target web output
only ever includes the current module as an one of the modules included.
With wasm-bindgen's optimization to import directly from modules,
however, it's possible to have more modules imported from in the
generated wasm file. This commit ensures that the imports are hooked up
in the --target web es6 emulation mode, ensuring there aren't
extraneous errors about import objects.

@alexcrichton alexcrichton requested a review from fitzgen May 1, 2019 18:58
Currently the import object constructed for the `--target web` output
only ever includes the current module as an one of the modules included.
With `wasm-bindgen`'s optimization to import directly from modules,
however, it's possible to have more modules imported from in the
generated wasm file. This commit ensures that the imports are hooked up
in the `--target web` es6 emulation mode, ensuring there aren't
extraneous errors about import objects.
@alexcrichton alexcrichton merged commit a13eb10 into wasm-bindgen:master May 1, 2019
@alexcrichton alexcrichton deleted the fix-web-imports branch May 1, 2019 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants