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

WASM / node.js support broken with Rust nightly #78

Closed
mpalmer opened this issue Nov 22, 2024 · 7 comments · Fixed by #80
Closed

WASM / node.js support broken with Rust nightly #78

mpalmer opened this issue Nov 22, 2024 · 7 comments · Fixed by #80
Labels
help wanted Extra attention is needed nodejs Issue relates specifically to experimental NodeJS support pr-welcome This would be a good fix/feature, but the maintainer isn't planning on doing the work

Comments

@mpalmer
Copy link
Owner

mpalmer commented Nov 22, 2024

Per this check run, it looks like something in Rust nightly is unhappy with the current WASM support. @award28 / @bcheidemann, are either of you able to take a look and fix it? Otherwise, I'll probably just have to rip out all the WASM stuff, as I'm not able to maintain it myself.

@bcheidemann
Copy link
Contributor

bcheidemann commented Nov 22, 2024

Per this check run, it looks like something in Rust nightly is unhappy with the current WASM support. @award28 / @bcheidemann, are either of you able to take a look and fix it? Otherwise, I'll probably just have to rip out all the WASM stuff, as I'm not able to maintain it myself.

Hey @mpalmer,

Happy to take a look over the weekend 🙂 Currently we're just shy of 10k weekly downloads on NPM so would be a shame to drop support as it's clearly useful for people!

@mpalmer mpalmer added help wanted Extra attention is needed pr-welcome This would be a good fix/feature, but the maintainer isn't planning on doing the work nodejs Issue relates specifically to experimental NodeJS support labels Nov 22, 2024
@mpalmer
Copy link
Owner Author

mpalmer commented Nov 22, 2024

Yeah, I don't want to rip it out either, but my supply of round tuits is perilously low, and it's not great having a perma-broken CI check...

@bcheidemann
Copy link
Contributor

Yeah, I don't want to rip it out either, but my supply of round tuits is perilously low, and it's not great having a perma-broken CI check...

I can certainly empathise with this 🤪

Is this an isolated incident or is Node.js support making your life difficult more generally? If so, I'd love to try and find a way we can make it more sustainable.

@mpalmer
Copy link
Owner Author

mpalmer commented Nov 25, 2024

There's a couple of other issues tagged nodejs, but they're not show-stoppers. The only problem (other than this CI failure, which you've now tamed, yay!) related to WASM was in #76, where the difference in behaviour with the npm-provided executable (and lack of super-clear indication that it wasn't the native binary) caused some brief confusion, but we got it figured out.

Probably the biggest ongoing offence against my incipient OCD is the two open PRs, which are both WASM-related, but I avoid any problems by just not looking at them. 😀

@bcheidemann
Copy link
Contributor

Probably the biggest ongoing offence against my incipient OCD is the two open PRs

Yeah, at this point I'm lacking a bit of context for those PRs, but I'll carve out some time to re-familiarise myself with them and try to get them over the line.

There's a couple of other issues tagged nodejs, but they're not show-stoppers.

I'll check these out as well.

My own supply of round tuits is also a little lower than I'd like, but I'd like to allocate some of them to this project - only fair given I pushed for Node.js support in the first place! 🙂

@bcheidemann
Copy link
Contributor

Leaving this here mostly for my own reference:

As per rustwasm/wasm-bindgen#4283 the upstream cause of this issue is now fixed and we should be seeing a patch release soon in wasm-bindgen very soon. Once we have a patch release, we should be able to revert this change.

@bcheidemann
Copy link
Contributor

@mpalmer as per the above comment #80 can now be reverted. I've tested on my local and raised #81 to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed nodejs Issue relates specifically to experimental NodeJS support pr-welcome This would be a good fix/feature, but the maintainer isn't planning on doing the work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants