HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wasm-bindgen
wasm-pack
Rust2020–2024
wasm-bindgen / wasm-pack

wasm-pack

📦✨ your favorite rust -> wasm workflow tool!

8Distinct people
9Mentions
0Explicit recommenders
7.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

📦✨ your favorite rust -> wasm workflow tool!

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2020-01-05 19:02:17 UTC to 2024-04-22 23:42:49 UTC.

0123452020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

9 sources
What trend? Forking happens all the time. It's one of the benefits of open source. I've often made PRs on github to projects while shifting projects I work on to my fork since upstreaming can take months or often never happen Granted, Nuitka is an active project, but wasmer.io is going to have a much more focused desire with their changes that they can deploy, meanwhile getting it upstream will have to go through rounds of review & adjustments https://github.com/rustwasm/wasm-pack/pull/937 this small change took over 2 years to merge. Open source takes time
In Py2wasm – A Python to WASM Compiler
That's true - the package is auto-generated using [wasmpak](https://github.com/rustwasm/wasm-pack), that's why TypeScript definitions are clunky. I did the initial prql-js release and I'm actually not sure about the free() issue you are talking about. We are currently working on compiling it for both Node.js and the browser target, and would be happy to see some advice if you are familiar with WASM!
In Show HN: PRQL 0.2 – a better SQL
> Since no alternative has presented itself, every time I revisit wasm-pack I’m pained by new potholes that have risen due to neglect I've had open PRs for a year now: https://github.com/rustwasm/wasm-pack/pull/937 https://github.com/rustwasm/wasm-pack/pull/1089 Very straight forward changes. Emailed Ashley about helping with wasm-pack, no response (in response to https://github.com/rustwasm/wasm-pack/issues/928) Updates to wasm-bindgen shouldn't require a change to wasm-pack. It should expose ways to pass arbitrary flags down While having a webpack plugin is nice, I since gave up on wasm-pack & added a build-wasm to my package.json's scripts: https://github.com/serprex/openEtG/commit/9997fb098d168920bb... This way if someone wants to contribute to openetg they don't need to install my wasm-pack fork. Ideally wasm-pack-plugin would skip w
Read the rest
asm-pack & use wasm-bindgen directly I do hope wasm-bindgen is able to be adequately resourced. It's a pleasure to program wasm modules in Rust
In Authoring a SIMD enhanced WASM library with Rust
In The [Rust] Core Team Is Toxic
I think there are a couple important details you are missing... First, wasm-pack is not Ashley's personal project, it is an official Rust Wasm project. That means it is owned by the Rust Wasm team, and it is maintained by the Rust Wasm team. It is an official part of Rust, similar to how cargo and rustdoc are an official part of Rust. wasm-pack was never intended to be maintained only by Ashley. Multiple Rust Wasm Core team members (including myself) politely asked Ashley multiple times to transfer publishing rights to the Rust Wasm Core team (which she was supposed to have done months ago), but she refused. Multiple people had politely offered to take over maintenance of wasm-pack (when it was clear that Ashley was unwilling to do so), but once again she refused. She knew how important wasm-pack is to Rust Wasm, but she did not want to g
Read the rest
ive up control and power, even though it wasn't even supposed to be her package in the first place. Second, forking is not as simple or as easy as you claim... forking is something that has a very high cost, so it should be done as a last resort. wasm-pack is an official Rust package (and it is vital to Rust Wasm), and so forking it would have a lot of costs: * A new crate would have to be created (what should it be called? wasm-pack2?) * The GitHub repo would have to be changed or transferred. * Multiple different documentation websites (including the official Rust website) would need to be updated. * A newsletter would need to be sent out informing everybody of the change. * All existing projects would need to switch to the new package. * The old package would still exist, which would be very confusing for people, especially because many tutorials and blogs would still be referring to the old wasm-pack! * Ashley herself would throw a huge tantrum over it, because she would view it as taking control away from herself. And because she is a Rust Core team member, her tantrum would have power behind it. Forking is absolutely NOT an appropriate solution in this case. Ashley's behavior was simply wrong, unacceptable, and reflects very poorly on the Rust team (which she is a part of). As for Ashley's personal character... before she worked for Rust, she worked for npm. While she was working there, she tried to falsely accuse Rod Vagg because she wanted to kick him out of npm. Thankfully she failed, and after she failed she quit npm: https://thenewstack.io/node-js-forked-complaints-repeated-ha... https://medium.com/@rvagg/the-truth-about-rod-vagg-f063f6a53... While she was working for npm, she violated npm's Code of Conduct numerous times, saying incredibly horrible sexist and racist things such as "kill all men", and actively trying to prevent white men from speaking at tech conferences: https://archive.fo/f10KK No, she was not joking, and even if it was "just a joke" it is unacceptable. If a man said "kill all women" even as a joke he would be immediately fired and blacklisted from all companies. Despite all of this, she was still hired onto the Rust Core team, because she is in a romantic relationship with Steve Klabnik (nepotism). Interestingly, Steve Klabnik is also the same person who is smearing Amazon because Amazon denied a job to Ashley. The Rust Core team was aware of Ashley's past behavior, yet they hired her anyways. And even though numerous people spoke out about this, they were silenced and censored by the Rust team: https://internals.rust-lang.org/t/announcement-ashley-willia... Ashley also abused her moderator powers to ban dakom, even though he had done nothing wrong: https://github.com/rustwasm/wasm-pack/issues/914 https://github.com/rustwasm/wasm-pack/issues/928 She also made numerous lies in those two threads (such as claiming that the Rust Wasm Core team is "random people without organization", the Rust Wasm Core team is hand-picked, they are the official leaders of Rust Wasm). She acted incredibly disrespectful toward the Rust Wasm team (who worked very hard to make Rust work on Wasm), even though she had contributed basically nothing. There is a dark side to Rust, which everybody is afraid to talk about. Anybody who tries to discuss things is censored by the Rust Core team. That's why I stopped contributing to Rust and I will never go back.
In I refuse to let Amazon define Rust
An unfortunate blemish on her record is her handling of `wasm-pack`. She worked to ensure it become a critical part of the Rust/Wasm ecosystem and then silently stopped maintaining it. For most of 2020 / 2021 `wasm-pack` was not updated with pull requests and security fixes because Ashley did not transfer publish rights. Even though `wasm-pack` became unusable for many users it was still described as necessary in the official Rust / Wasm tutorials. Likely this set back the Rust/Wasm ecosystem by discouraging many new members. It would have been far better if she just spoke up and asked for help. It seems she wanted to ignore a problem she didn't want to deal with, which I can relate to, but that's not a good quality in an executive director. Some relevant GitHub issues: https://github.com/rustwasm/wasm-pack/issues/914 https://github.com/r
Read the rest
In I refuse to let Amazon define Rust
Rust has the best tooling for wasm and is easiest to get started with, in my opinion. `rustup target add wasm32-unknown-unknown` `cargo build --target=wasm32-unknown-unknown` Is all you need to compile a Rust library to a `.wasm` file. (almost, you also need a setting in Cargo.toml: [lib] crate-type = ["cdylib", "rlib"] ) In the browser you can get access to DOM apis via web-sys. The documentation has quite a lot of examples and info: https://rustwasm.github.io/wasm-bindgen/web-sys/index.html wasm-pack (https://github.com/rustwasm/wasm-pack) makes building code for the browser easy.
In WebAssembly Studio

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.