Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade wasm-pack from 0.12.1 to 0.13.0 #10

Closed
wants to merge 1 commit into from

Conversation

yeskiy
Copy link
Owner

@yeskiy yeskiy commented Jul 23, 2024

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade wasm-pack from 0.12.1 to 0.13.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released on 22 days ago.

Release notes
Package name: wasm-pack
  • 0.13.0 - 2024-07-01
    • ✨ 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

  • 0.12.1 - 2023-06-27
    • 🤕 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.

from wasm-pack GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade wasm-pack from 0.12.1 to 0.13.0.

See this package in npm:
wasm-pack

See this project in Snyk:
https://app.snyk.io/org/yeskiy/project/a539549e-ffa9-414a-9b0e-62de9e25a407?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sonarcloud bot commented Jul 23, 2024

@yeskiy yeskiy closed this Oct 29, 2024
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.

2 participants