v0.23.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#​3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#​3818)

  When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  
  // New output (with --jsx=preserve)
  <Foo>
    <Bar />
  </Foo>;

v1.0.204

Compare Source

• Apply #[diagnostic::on_unimplemented] attribute on Rust 1.78+ to suggest adding serde derive or enabling a "serde" feature flag in dependencies (#​2767, thanks @​weiznich)

v1.0.120

Compare Source

• Correctly specify required version of indexmap dependency (#​1152, thanks @​cforycki)

v2.0.69

Compare Source

• Correctly parenthesize labeled loops inside a break value (#​1692)
• Add Punctuated::get and get_mut (#​1693)

v0.13.0

Compare Source

• ✨ 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

  • Fix error and warnings in install script - lucashorward, issue/1159, issue/1217, issue/1283, pull/1320

  • Bump follow-redirects from 1.14.9 to 1.15.6 in /npm - dependabot, pull/1375

  • Bump rustls-webpki from 0.100.1 to 0.100.2 - dependabot, pull/1323

  • Bump rustix from 0.37.20 to 0.37.25 - dependabot, pull/1341

  • Bump rustls from 0.21.9 to 0.21.11 - dependabot, pull/1385

  • Bump tar from 6.1.11 to 6.2.1 in /npm - dependabot, pull/1379

• 📖 Documentation

  • Fix typo in README - Lionelf329, [pull/1368]

  • Add a description of build --target deno - puxiao, pull/1344

  • Document deno in build target - sigmaSd, pull/1348

  • Fix local navigation backing one step too far in docs - SamuSoft, pull/1387

  • Add --target web to quick start build command - josephrocca, pull/1367