Skip to content

Add support for JavascriptCore in NAPI#31

Open
syrusakbary wants to merge 5 commits into
mainfrom
napi-jsc
Open

Add support for JavascriptCore in NAPI#31
syrusakbary wants to merge 5 commits into
mainfrom
napi-jsc

Conversation

@syrusakbary

Copy link
Copy Markdown
Member

Add support for JavascriptCore in NAPI

# Conflicts:
#	.github/workflows/test-and-build.yml
rbbydotdev added a commit to rbbydotdev/edgejs that referenced this pull request May 30, 2026
Replaces the ?-only StackBlitz column with measured-or-cited cells:
* ✓ for modules where real Node binary works and no carve-out applies
* ◐ / ✗ for documented bugs (crypto.createHmac issue wasmerio#31 since 2021,
  AES-256-CBC issue #1571 Oct 2024, worker_threads.unref #365,
  net: raw TCP/UDP blocked, dgram: no UDP)
* — for architectural impossibilities

Triple-confirmed StackBlitz publishes NO per-module compat matrix.
Their tracking happens via GitHub issues + categorical
troubleshooting page + an AI-agents test suite that bundles built-ins
into one pass/fail bucket.

Bun cells annotated with verbatim Node-suite pass percentages from
their docs:
* assert/events/path/os/querystring/string_decoder/punycode: 100%
* zlib: 98%, fs: 92%, dgram: >90%, dns: >90%
* http: no percentage (caveat about outgoing client body buffering)
* http2: 95% gRPC-suite (not Node-suite — flagged)

Added a `punycode` row (Bun calls it out specifically) and a
"Native addons" row covering the no-`.node` constraint shared
across browser runtimes.

Updated Sources section with StackBlitz GitHub issue cites + a
"surprises worth flagging" callout in Updating-this-doc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants