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
5 changes: 5 additions & 0 deletions .changeset/oxc-fallback.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@node-core/doc-kit': patch
---

Fall back to WASM when a native OXC binding is unavailable
58 changes: 45 additions & 13 deletions package-lock.json

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

1 change: 1 addition & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@
"@node-core/ui-components": "^1.7.0",
"@orama/orama": "^3.1.18",
"@orama/ui": "^1.5.4",
"@oxc-parser/binding-wasm32-wasi": "^0.140.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

WASM binding version mismatch

High Severity

The new direct dependency on @oxc-parser/binding-wasm32-wasi is pinned to ^0.140.0 while oxc-parser remains at ^0.139.0. OXC expects parser and platform bindings to share the same release. When the optional nested 0.139.0 WASM package is not installed, Node resolves the hoisted 0.140.0 binding for a 0.139.0 parser—the exact fallback path this change targets.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 8fed169. Configure here.

"@rollup/plugin-virtual": "^3.0.2",
"@swc/html-wasm": "^1.15.43",
"acorn": "^8.17.0",
Expand Down
Loading