-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
bump wasm-bindgen to 0.2.51 #681
Conversation
It may be worth mentioning that in my app, I'm using |
This new version of wasm-bindgen is using async/await, so it will need Rust 1.0.39 or above which becomes stable in a month. |
@ctaggart I think the error in CI is the same error I was seeing on later versions of |
I'm able to reproduce the error in CI with:
To debug in chrome, just remove the
I think it is just the |
It reproduces with just: use wasm_bindgen_test::{wasm_bindgen_test, wasm_bindgen_test_configure};
wasm_bindgen_test_configure!(run_in_browser);
#[wasm_bindgen_test]
fn test_document() {
stdweb::web::document();
} |
I submitted the minimal test to koute/stdweb#373 |
Thanks for digging in! Are you sure this only affects tests? |
No, I am not. |
This needs to wait for stdweb 0.4.20 for compatibility. |
@ctaggart stdweb 0.4.20 is out! Want to give it a whirl? |
This test works for me locally now! Let's see if we can get CI to light up green too.
|
CI is green! I just need to remove the submodule changes. One sec. |
1671b75
to
e8a7fb4
Compare
Let's keep master on stable for now and have futures-related work live in the |
* upgrade wasm-bindgen to 0.2.51 * Run macro tests on beta and update readme * Update README.md * Update .travis.yml
* bump wasm-bindgen to 0.2.51 (#681) * upgrade wasm-bindgen to 0.2.51 * Run macro tests on beta and update readme * Update README.md * Update .travis.yml * implement send_future * cargo fmt * add todo question * static dispatch on Error in future * Add framework for example using futures * add a basic future to indicate that futures work * change example to fetch markdown instead of just resolving a string * remove unnneded import * Force users to handle errors in their future * Force users to handle errors in their future * cleanup and introduction of FetchState * respond to feedback * update comment * fix cargo.toml dependency issues
* bump wasm-bindgen to 0.2.51 (yewstack#681) * upgrade wasm-bindgen to 0.2.51 * Run macro tests on beta and update readme * Update README.md * Update .travis.yml * implement send_future * cargo fmt * add todo question * static dispatch on Error in future * Add framework for example using futures * add a basic future to indicate that futures work * change example to fetch markdown instead of just resolving a string * remove unnneded import * Force users to handle errors in their future * Force users to handle errors in their future * cleanup and introduction of FetchState * respond to feedback * update comment * fix cargo.toml dependency issues
I think the problems in #586 go away with wasm-bindgen 0.2.51. My app compiles and runs with this combination.