Skip to content
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

Broken with latest version of wasm-bindgen #30

Closed
Pauan opened this issue May 2, 2020 · 1 comment · Fixed by #31
Closed

Broken with latest version of wasm-bindgen #30

Pauan opened this issue May 2, 2020 · 1 comment · Fixed by #31

Comments

@Pauan
Copy link

Pauan commented May 2, 2020

This was first reported here: rustwasm/wasm-bindgen#2120

The problem is that wasm-bindgen changed its code generation, and since this plugin does custom parsing of the JS code, that is now broken.

In addition, wasm-bindgen now generates a foo_bg.js file (rather than foo.js), so the file path needs to be updated as well.

However, most of this complexity can be avoided by using --target web. Then it wouldn't need to do custom parsing, and it wouldn't need a custom init section either.

@kaoet
Copy link

kaoet commented May 9, 2020

Temporary workaround: in your Cargo.toml:

[dependencies]
wasm-bindgen = "0.2, <0.2.61"

That keeps you away from the broken 0.2.61+ version.

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 a pull request may close this issue.

2 participants