Skip to content

Update @emnapi/runtime 1.7.1 → 1.8.1 (minor) #19545

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.

Sign up for GitHub

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

Open
depfu wants to merge 1 commit into
base: main
Choose a base branch
from
+32 −10
Open

Update @emnapi/runtime 1.7.1 → 1.8.1 (minor) #19545

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion crates/node/npm/wasm32-wasi/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
"dependencies": {
"@napi-rs/wasm-runtime": "^1.1.1",
"@emnapi/core": "^1.7.1",
"@emnapi/runtime": "^1.7.1",
"@emnapi/runtime": "^1.8.1",
Comment on lines 31 to +32
Copy link

@coderabbitai coderabbitai bot Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

@emnapi/core npm package latest version

💡 Result:

The latest published version appears to be 1.7.1. [1][2]

Sources:

  • Socket.dev package listing (shows 1.7.1). [1]
  • npm package page (official npm listing shows older versions; double-check npm registry if you need definitive registry data). [2]

🌐 Web query:

@emnapi/runtime 1.8.1 @emnapi/core compatibility

💡 Result:

Short answer: Use matching versions — @emnapi/runtime 1.8.1 should be used with @emnapi/core 1.8.1. The emnapi README states “Each package should match the same version,” and the docs show @emnapi/runtime and @emnapi/core used together. [1][2]

Sources:

  • emnapi GitHub README — “Each package should match the same version.” [1]
  • emnapi docs / Getting Started (shows runtime + core used together). [2]

🌐 Web query:

@emnapi/core security vulnerabilities CVE

💡 Result:

I found no CVE entries for @emnapi/core and no direct vulnerabilities reported in major vulnerability trackers (npm package page and Snyk). [1][2]

Sources:
[1] npm package page for @emnapi/core. [2] Snyk vulnerability listing for @emnapi/core.

Update @emnapi/core to match @emnapi/runtime version.

The emnapi documentation explicitly requires that all @emnapi packages use matching versions. Currently, @emnapi/runtime is at 1.8.1 while @emnapi/core remains at 1.7.1. Update @emnapi/core to 1.8.1 to maintain version alignment, or downgrade @emnapi/runtime to 1.7.1 if 1.8.1 is not yet available for @emnapi/core.

🤖 Prompt for AI Agents 
In @crates/node/npm/wasm32-wasi/package.json around lines 31 - 32, The
package.json dependency versions for @emnapi are mismatched: "@emnapi/runtime"
is "^1.8.1" while "@emnapi/core" is "^1.7.1"; update the version string for
"@emnapi/core" to "^1.8.1" to match "@emnapi/runtime" (or if you prefer to lock
to 1.7.1, change "@emnapi/runtime" to "^1.7.1"), ensuring both @emnapi/core and
@emnapi/runtime use identical versions.

"@tybys/wasm-util": "^0.10.1",
"@emnapi/wasi-threads": "^1.1.0",
"tslib": "^2.4.0"
Expand Down
40 changes: 31 additions & 9 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.