Skip to content

Releases: rustwasm/wasm-pack

β˜€οΈ v0.13.1

29 Oct 18:36
Compare
Choose a tag to compare
  • ✨ Features

    • Requests using proxy settings from env - jjyr, pull/1438

      This enables ureq to use proxy settings from env, it solves lots of pain in network restricted environments.

  • πŸ€• Fixes

    • Update binary-install to v0.4.1 - drager, pull/1407

      Release v0.4.0 of binary-install introduced a regression that caused failures on some platforms. This release fixes that regression.

    • Allow npm binary upgrades - net, pull/1439

      Fixes an issue where upgrading wasm-pack via NPM would not update the underlying binary.
      Previously, the binary was stored in the binary-install package's directory without versioning, causing version upgrades to silently fail as the old binary continued to be used.
      The binary is now stored in node_modules/wasm-pack/binary/, ensuring proper version updates when upgrading the package.

      Before: Upgrading from 0.12.1 to 0.13.0 would continue using the 0.12.1 binary
      After: Each wasm-pack version manages its own binary, enabling proper version upgrades

  • πŸ› οΈ Maintenance

β˜€οΈ v0.13.0

01 Jul 18:57
Compare
Choose a tag to compare
  • ✨ Features

    • Add option to skip optimization with wasm-opt - sisou, pull/1321

      This feature introduces the --no-opt option to wasm-pack, providing a significant improvement in build efficiency for projects requiring multiple wasm-pack executions.

    • Add support geckodriver for linux-aarch64 - EstebanBorai, pull/1371

      Introduces support to download Geckodriver in Linux aarch64.

    • Add wasm-opt linux aarch64 condition - dkristia, issue/1392, pull/1393

      A linux aarch64 build for wasm-opt exists in the newest binaryen versions.

  • πŸ€• Fixes

    • Fix passing relative paths to cargo - dfaust, issue/704, issue/1156, issue/1252, pull/1331

      When building a crate located in a sub-directory, relative paths, passed as extra options to cargo (like --target-dir), are now handled correctly.

    • Rewrite wasm_target to use target-libdir - daidoji, issue/1342, pull/1343

      Rewritten wasm_target to use target libdir from the rustc tool rather than looking through sysroot. This is to accomodate non-rustup installations.

    • Declare ES module in package.json - gthb, issue/1039, pull/1061

      In bundler mode, generate package.json with "type": "module" and use the "main" attribute instead of the "module" attribute.

      This change makes the built ES module palatable to Node.js (when run with --experimental-vm-modules --experimental-wasm-modules),
      while it remains also palatable to webpack as illustrated in webpack/webpack#14313
      (where the pkg subfolder is generated with wasm-pack built with this change).
      This resolves the headache of using a wasm-pack-built package in a library that one needs to both run directly in Node and include in a webpack build.

    • Use new chromdriver endpoint and fix CI - Myriad-Dreamin, kade-robertson, issue/1315, issue/1390, pull/1325, pull/1391

    • Add mingw support to npm package - nathaniel-daniel, issue/1354, issue/1359, pull/1363

      Fixes the NPM package's platform detection for mingw.

    • pkg-dir option for pack and publish commands - danielronnkvist, issue/1369, pull/1370

      To be able to use these commands when the output directory option to the build command isn't the default pkg.

    • Optimize out-dir display - ahaoboy, issue/1395, pull/1396

      Optimize out-dir display.

      from:

      [INFO]: πŸ“¦ Your wasm pkg is ready to publish at /root/code/fib-wasm/fib-rs/../fib-wasm/wasm.

      to:

      [INFO]: πŸ“¦ Your wasm pkg is ready to publish at /root/code/fib-wasm/fib-wasm/wasm.

  • πŸ› οΈ Maintenance

  • πŸ“– Documentation

β˜€οΈ v0.12.1

27 Jun 20:22
Compare
Choose a tag to compare
  • πŸ€• Fixes

    • Restore --version command - lynn, issue/1301, pull/1305

      The --version command got lost in space in v0.12.0. It's now brought back!

    • Fix value parser for Option - Myriad-Dreamin, issue/1304, pull/1307

      A value parser for OsString cannot parse a command line argument for Option,
      which let it failed to specify paths for pack, publish and test commands, this faulty behavior
      was introduced in v0.12.0.

β˜€οΈ v0.12.0

17 Jun 11:21
Compare
Choose a tag to compare

🌦️ v0.11.1

11 May 18:15
9aff861
Compare
Choose a tag to compare

🌦️ v0.11.0

19 Mar 10:16
Compare
Choose a tag to compare

🌦️ v0.10.3

13 Jun 18:12
Compare
Choose a tag to compare
  • πŸ€• Fixes

    • Use bash to create release tarballs - nasso, issue/1097 pull/1144

      Fixes Windows installer failure due to malformatted tar.

    • Clean up package.json from previous runs - main--, issue/1110-comment pull/1119

      Remove the package.json file from previous runs to avoid crashes.

    • Do not remove the pkg directory - huntc, issue/1099 pull/1110

      A recent change ensured that the pkg directory was removed as the first step of attempting to create it.
      Unfortunately, this caused a problem for webpack when watching the pkg directory.
      Webpack was unable to recover its watching and so any watch server must be restarted,
      which is a blocker when using it. This PR and release fixes this.

    • Bump regex from 1.5.4 to 1.5.6 - dependabot, pull/1147

      Version 1.5.5 of the regex crate fixed a security bug in the regex compiler.

    • Bump openssl-src from 111.17.0+1.1.1m to 111.20.0+1.1.1o - dependabot, pull/1146

      Bring in bug fixes from the new version of openssl-src.

🌦️ 0.10.2

16 Dec 19:41
Compare
Choose a tag to compare
  • ✨ Features

  • πŸ€• Fixes

    • Add support for macos aarch64 - d3lm, issue/913 pull/1088

      This fixes aarch64 for MacOS and will download x86_64-apple-darwin.

    • Add linux/arm64 to release workflow - nacardin, issue/1064 pull/1065

    • Force axios version - drager, pull/1094

      Forces npm package axios to version 0.21.2 in order to get security fix for a security vulnerability present in axios before version 0.21.2.

🌦️ 0.10.1

06 Sep 18:35
Compare
Choose a tag to compare

🌦️ 0.10.0

02 Jul 12:25
Compare
Choose a tag to compare
  • ✨ Features

    • Added keywords - lucashorward, issue/707 pull/838

      package.json files usually contain a keywords array so that npm can make searching easier.
      This PR extracts keywords from Cargo.toml and puts them into package.json.

  • πŸ€• Fixes

    • Update binary-install to get fix for axios security vulnerability - simlay, Rizary, issue/958 pull/973 pull/1012

      Updates binary-install npm package to version ^0.1.0 in order to get security fix for a security vulnerability in axios.

    • Fix cargo-generate installation - bradyjoslin, issue/975 issue/907 pull/983

      wasm-pack new hello-wasm didn't work due to a bad link when trying to install cargo-generate.

      This PR points the installation to the correct place and makes wasm-pack new working again!

    • Pass through extra options when building tests - azriel91, issue/698 pull/851

      wasm-pack test accepts extra options to pass through to cargo when running tests.
      Under the hood, this runs cargo build before cargo test, and the additional options were only passed through to the test command. This meant that crates that enabled native features by default could not be built using wasm-pack, as it would attempt to build tests for the wasm32-unknown-unknown target with the native features enabled.

      This PR passes through the extra options to cargo when building the tests as well.

    • Corrected files included in package.json for bundler / no target - lucashorward, issue/837 pull/839

      wasm-pack build and wasm-pack build --target bundler generates a _bg.js file, but it was not added to the package.json.
      The file that is added, *.js will however reference the _bg.js, so when the package was distributed (both through pack or publish) it is not usable.

      This PR includes that _bg.js file in package.json.

    • Find the main package if multiple packages have the same name - ghost, pull/830

      If there were 2 packages with the same name, wasm-pack would sometimes use the wrong one and errored.

  • πŸ“– Documentation

  • πŸ› οΈ Maintenance