test(napi/parser): test wasi browser

[hi-ogawa]

This adds (almost) e2e testing of oxc-parser on browser using Vitest browser mode.

How to test locally:

cd napi/parser
pnpm build-wasi
pnpm build-npm-dir
pnpm test-browser  # before this, you'll likely need `pnpm exec playwright install chromium`

I said "almost" because this doesn't test the exact scenario when oxc-parser and @oxc-parser/binding-wasm32-wasi are installed under node_modules, which can cause bundlers to behavior differently (especially Vite unbundled dev). Nonetheless, this should verify functional napi-rs setup for browser. I think we can separately create a sample Vite app on stackblitz for doc purpose, which requires optimizeDeps.exclude and other gotchas.

todo

• run it on ci
• test other napi-rs pakcages?

[hi-ogawa]

• test(napi/parser): test wasi browser #9793 👈 (View in Graphite)
• feat(napi/parser): JSON.parse the returned AST in wasm #9630
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.