Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@
"browser": "tailwindcss-oxide.wasi-browser.js",
"dependencies": {
"@napi-rs/wasm-runtime": "^1.1.1",
"@emnapi/core": "^1.7.1",
"@emnapi/core": "^1.8.1",
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

cat crates/node/npm/wasm32-wasi/package.json

Repository: tailwindlabs/tailwindcss

Length of output: 1109


🏁 Script executed:

# Check if @emnapi/core version 1.8.1 exists and get version info
npm view @emnapi/[email protected] version 2>&1 || echo "Version not found or npm unavailable"
npm view @emnapi/core versions --json 2>&1 | tail -20

Repository: tailwindlabs/tailwindcss

Length of output: 284


🌐 Web query:

@emnapi/core 1.8.1 npm package release changelog features

💡 Result:

I couldn't find an official changelog or release notes specifically listing the features for @emnapi/core v1.8.1. NPM/Snyk show v1.8.1 as the latest published version, but the repository's GitHub release/tags or a CHANGELOG.md referencing 1.8.1 wasn't found in my search. Sources checked:

  • @emnapi/core package pages on npm. [1][2]
  • Snyk package page showing latest version 1.8.1. [3]
  • emnapi GitHub repository (no release notes/CHANGELOG entry for 1.8.1 found). [4]

If you want, I can:

  • Check the repo tags/releases again and open the v1.8.1 tag if present, or
  • Inspect the package tarball from the npm registry to extract the publish commit / package.json / changelog contents.

Which would you prefer?


🌐 Web query:

@emnapi/runtime @emnapi/core compatibility version requirements

💡 Result:

Short answer: @emnapi/runtime and @emnapi/core must use the same package version — install matching versions (exactly the same release). [1][2]

Sources:

  • emnapi Getting Started (tips: "Each package should match the same version"). [1]
  • emnapi npm page (same recommendation). [2]

Update @emnapi/runtime to ^1.8.1 to match @emnapi/core.

The @emnapi packages require matching versions. Both @emnapi/core (line 31) and @emnapi/runtime (line 32) must be at the same version. Update @emnapi/runtime from ^1.7.1 to ^1.8.1.

🤖 Prompt for AI Agents
In @crates/node/npm/wasm32-wasi/package.json at line 31, Update the dependency
version for @emnapi/runtime to match @emnapi/core by changing the
@emnapi/runtime entry from ^1.7.1 to ^1.8.1 in package.json so both @emnapi/core
and @emnapi/runtime use ^1.8.1; ensure package.json has "@emnapi/runtime":
"^1.8.1" and run your package manager install to update lockfiles.

"@emnapi/runtime": "^1.7.1",
"@tybys/wasm-util": "^0.10.1",
"@emnapi/wasi-threads": "^1.1.0",
Expand Down
33 changes: 28 additions & 5 deletions pnpm-lock.yaml

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