Skip to content

chore(deps): update npm packages#4092

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/npm-packages
Jul 7, 2024
Merged

chore(deps): update npm packages#4092
renovate[bot] merged 1 commit intomainfrom
renovate/npm-packages

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 7, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 9.4.0 -> 9.5.0 age adoption passing confidence
wasm-pack ^0.12.1 -> ^0.13.0 age adoption passing confidence

Release Notes

pnpm/pnpm (pnpm)

v9.5.0

Compare Source

rustwasm/wasm-pack (wasm-pack)

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

  • 📖 Documentation


Configuration

📅 Schedule: Branch creation - "before 10am on monday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Jul 7, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

@renovate renovate bot merged commit 57d821b into main Jul 7, 2024
@renovate renovate bot deleted the renovate/npm-packages branch July 7, 2024 18:33
@graphite-app
Copy link
Contributor

graphite-app bot commented Jul 7, 2024

Your org has enabled the Graphite merge queue for merging into main

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants