[Snyk] Upgrade wasm-pack from 0.12.1 to 0.13.0 #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
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
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
0.12.1 - 2023-06-27
-
-
-
from wasm-pack GitHub release notes✨ Features
Add option to skip optimization with wasm-opt - sisou, pull/1321
This feature introduces the
--no-optoption 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
🤕 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.
Important
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: