Update @napi-rs/wasm-runtime 1.1.0 → 1.1.1 (patch)#19527
Conversation
WalkthroughThis pull request updates the Pre-merge checks✅ Passed checks (2 passed)
📜 Recent review detailsConfiguration used: Repository UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI Agents
In @crates/node/npm/wasm32-wasi/package.json:
- Line 30: The package.json dependency for "@napi-rs/wasm-runtime" references a
non-existent version "^1.1.1"; update that version string to a published release
(e.g., "^1.1.0" or "^1.0.3") in the dependency list, then regenerate the
lockfile by running the package manager (npm install / npm ci) so the resolved
version is recorded; ensure the change is made to the dependency entry for
"@napi-rs/wasm-runtime" and include the updated lockfile in the commit.
📜 Review details
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
crates/node/npm/wasm32-wasi/package.jsoncrates/node/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
- GitHub Check: Linux / oxide
- GitHub Check: Linux / postcss
- GitHub Check: Linux / upgrade
- GitHub Check: Windows
- GitHub Check: macOS
- GitHub Check: Linux / cli
- GitHub Check: Linux / vite
- GitHub Check: Linux
🔇 Additional comments (1)
crates/node/package.json (1)
37-37: LGTM! Consistent dependency update.The devDependency version update is consistent with the dependency update in
crates/node/npm/wasm32-wasi/package.json. Both files are correctly updated to version 1.1.1.
| "browser": "tailwindcss-oxide.wasi-browser.js", | ||
| "dependencies": { | ||
| "@napi-rs/wasm-runtime": "^1.1.0", | ||
| "@napi-rs/wasm-runtime": "^1.1.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@napi-rs/wasm-runtime version 1.1.1 npm package releases changelog
💡 Result:
I couldn’t find a published @napi-rs/wasm-runtime v1.1.1 or a changelog for that version. The npm registry shows latest published v1.0.3, and CDN/registry listings indicate v1.1.0 as a published tag — but no v1.1.1 release was found. [1][2][3]
Sources:
- npm package page (shows v1.0.3 as current on npm). [1]
- jsDelivr / package listing (shows v1.1.0). [2]
- Yarn/package index (version history showing v1.1.0 as latest tag). [3]
If you want, I can:
- search the napi-rs GitHub releases/tags and produce a changelog for the latest actual release, or
- notify you if/when v1.1.1 appears and fetch its changelog.
🌐 Web query:
@napi-rs/wasm-runtime security vulnerabilities CVE
💡 Result:
No known CVEs have been reported for the @napi-rs/wasm-runtime package as of Jan 6, 2026 — security scanners (Snyk, ReversingLabs) show no direct vulnerabilities for the package. [1][2] (Note: there are CVEs for other Wasm runtimes such as WAMR/Wasmer/Wasmtime, but those affect different projects, not @napi-rs/wasm-runtime.) [3]
Sources:
- Snyk package page for @napi-rs/wasm-runtime. [1]
- ReversingLabs / Spectra Assure scan for @napi-rs/wasm-runtime. [2]
- Example NVD entry for a Wasm runtime CVE (WAMR) — included to show related but separate runtime CVEs. [3]
🏁 Script executed:
cat -n crates/node/npm/wasm32-wasi/package.json | grep -A 2 -B 2 "@napi-rs/wasm-runtime"Repository: tailwindlabs/tailwindcss
Length of output: 416
Version @napi-rs/wasm-runtime@1.1.1 does not exist on npm.
The npm registry shows v1.0.3 as the latest published release, and v1.1.0 exists but v1.1.1 does not. With the caret constraint (^1.1.1), npm will fail to resolve this dependency during installation. Update to either ^1.1.0 or ^1.0.3 depending on which is the intended version.
🤖 Prompt for AI Agents
In @crates/node/npm/wasm32-wasi/package.json at line 30, The package.json
dependency for "@napi-rs/wasm-runtime" references a non-existent version
"^1.1.1"; update that version string to a published release (e.g., "^1.1.0" or
"^1.0.3") in the dependency list, then regenerate the lockfile by running the
package manager (npm install / npm ci) so the resolved version is recorded;
ensure the change is made to the dependency entry for "@napi-rs/wasm-runtime"
and include the updated lockfile in the commit.
There was a problem hiding this comment.
It does exist, that's why it got updated.
There was a problem hiding this comment.
Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!
|
Sorry, but the merge failed with:
|
|
@depfu rebase |
a429ae7 to
ce8fd46
Compare
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @napi-rs/wasm-runtime (1.1.0 → 1.1.1) · Repo
Sorry, we couldn't find anything useful about this release.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands