# Installer wasm-pack avec Homebrew, apk, MacPorts, Nix, pacman, zypper Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de wasm-pack pour les workflows d'agents IA. ## installation ```sh sudo av install brew:wasm-pack ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install wasm-pack ``` Preuve: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install wasm-pack ``` Preuve: MacPorts ports tree: devel/wasm-pack/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - apk (92%): ```sh sudo apk add wasm-pack ``` Preuve: Alpine Linux edge package indexes: wasm-pack from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Nix (92%): ```sh nix profile install nixpkgs#wasm-pack ``` Preuve: nixpkgs package indexes: pkgs/by-name/wa/wasm-pack/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S wasm-pack ``` Preuve: Arch Linux sync databases: wasm-pack from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz - zypper (92%): ```sh sudo zypper install wasm-pack ``` Preuve: openSUSE Tumbleweed package metadata: wasm-pack from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst ## Faits du paquet - **Clé du paquet:** brew:wasm-pack - **Gestionnaire de paquets:** Homebrew - **Version:** 0.15.0 - **Résumé source:** Your favorite rust -> wasm workflow tool! - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-07-17T22:47:12+09:00 - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - wasm-pack (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 0.15.0 ## Historique du projet et usages wasm-pack is the Rust-to-WebAssembly workflow tool that turns a Rust crate into a JavaScript-consumable package. It automates the boring path from Cargo project to WebAssembly binary, wasm-bindgen glue, generated `package.json`, README copy, and npm-ready `pkg` directory. ### Historique du projet The wasm-pack repository was created on February 12, 2018. Mozilla introduced it publicly in April 2018 as a tool for assembling and packaging Rust crates that target WebAssembly, explicitly aimed at letting Rust developers produce npm packages and JavaScript developers consume them without installing a Rust toolchain. From the start, wasm-pack was described as workflow glue rather than a compiler. It adds the `wasm32-unknown-unknown` target when needed, builds Rust in release mode, runs wasm-bindgen, moves generated files into `pkg`, creates a package manifest, and prepares documentation for the JavaScript package ecosystem. The Rust/Wasm 2019 roadmap made polishing the toolchain and culminating in a 1.0 version of wasm-pack one of its explicit goals. That placed wasm-pack at the center of the working group's push from experimental Rust/Wasm demos toward stable, batteries-included workflows. ### Historique d'adoption wasm-pack became the default tutorial path for Rust used inside web applications. MDN's Rust-to-Wasm guide teaches the workflow with wasm-pack and explains that the resulting package contains WebAssembly and JavaScript code, so downstream users do not need Rust installed and may not know the implementation language. The tool's ecosystem role is partly historical. The 2025 Rust post sunsetting the old rustwasm organization marked the end of the working-group hub that incubated tools like wasm-pack, while wasm-bindgen itself moved forward under new maintenance. wasm-pack remains useful and packaged, but it belongs to that first generation of Rust/Wasm workflow tools. ### Modes d'utilisation A typical project runs `wasm-pack build` from a Rust library crate. The tool compiles for WebAssembly, invokes wasm-bindgen, writes JS and TypeScript-facing artifacts, creates `pkg/package.json`, and can target bundlers, Node.js, or web usage depending on options. For maintainers, wasm-pack is the packaging bridge: Cargo metadata becomes npm metadata, Rust README material is copied into the package, and the generated JavaScript/Wasm files are laid out so ordinary npm, webpack, or other JavaScript tooling can consume them. ### Pourquoi les passionnés de paquets s'y intéressent wasm-pack is significant because it translated Rust's package culture into npm's package culture. It made a compiled Rust library look like a normal JavaScript dependency, which was essential for early Rust/WebAssembly adoption in frontend and Node workflows. ### Chronologie - 2018-02-12: Public GitHub repository created. - 2018-04-18: Mozilla Hacks introduces wasm-pack to Rust and JavaScript developers. - 2019-01-23: Rust/Wasm roadmap names wasm-pack 1.0 as a workflow milestone. - 2024-10-29: GitHub releases show v0.13.1 in the long-running 0.x series. - 2026-05-15: GitHub releases show v0.15.0 as the latest release at research time. ### Related projects - wasm-pack wraps wasm-bindgen and sits alongside cargo-generate templates, webpack or other JavaScript bundlers, npm, crates.io, and Rust's `wasm32-unknown-unknown` target. ### Sources - - - - - - ## Notes de sécurité Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour wasm-pack. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable. ## Autres enregistrements de gestionnaires de paquets - Nix - wasm-pack: normalized package name match | nixpkgs package indexes: pkgs/by-name/wa/wasm-pack/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - wasm-pack - 0.15.0-r1: normalized package name match | Alpine Linux edge package indexes: wasm-pack from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | rust to wasm build tool | https://github.com/wasm-bindgen/wasm-pack - pacman - wasm-pack - 0.15.0-1: normalized package name match | Arch Linux sync databases: wasm-pack from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Your favorite rust -> wasm workflow tool! | https://github.com/rustwasm/wasm-pack - zypper - wasm-pack - 0.13.1-1.6: normalized package name match | openSUSE Tumbleweed package metadata: wasm-pack from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Your favorite Rust → Wasm workflow tool! | https://github.com/rustwasm/wasm-pack - MacPorts - wasm-pack: normalized package name match | MacPorts ports tree: devel/wasm-pack/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Liens liés - [wasm-pack](https://pkg.so/fr/pkg/cargo/wasm-pack/) - Same normalized package name exists in another local package ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/wasm-pack.yml](https://github.com/mxcl/pkgdb/blob/main/combined/wasm-pack.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph