@oxc-parser/binding-wasm32-wasi returns parsed program as string

[hi-ogawa]

reproduction: https://stackblitz.com/github/hi-ogawa/reproductions/tree/main/oxc-wasi-vite?file=src%2Fmain.js
(Github repo https://github.com/hi-ogawa/reproductions/tree/main/oxc-wasi-vite)

I tested @oxc-parser/binding-wasm32-wasi on browser and ParseResult.program is returned as raw string.

const lib = await import("@oxc-parser/binding-wasm32-wasi/parser.wasi-browser.js");
const result = lib.parseSync("test.js", `let foo`);
const program = result.program;
console.log(typeof program)  // => 'string'

[Boshen]

I totally forgot about this. I was just wondering why I haven't removed @oxc-parser/wasm yet.

Draft PR: #9630

[hi-ogawa]

Oh right, @oxc-parser/binding-wasm32-wasi returning string is probably expected, but oxc-parser needs a proper wrapper entrypoint for browser/vite usage.

---

Additional note: My vite sample app currently relies on some hack https://github.com/hi-ogawa/reproductions/blob/0ca5023420efe071b553e65e99b175a0905d9d85/oxc-wasi-vite/vite.config.ts#L17. This could be a vite bug and also this can be probably worked around on napi-rs generation. I'm going to check this from both side.

• Vite issue ?url query import sometimes returns asset itself instead of url when used in external package with optimizeDeps.exclude vitejs/vite#19639
• Napi-rs side change fix(cli): use new URL instead of ?url for browser wasm fetching napi-rs/napi-rs#2511

[hi-ogawa]

I was just wondering why I haven't removed @oxc-parser/wasm yet.

Currently napi-rs's browser output is not as bundler agnostic as @oxc-parser/wasm/web, so this can potentially block some from moving it to oxc-parser easily. I made an issue about this on napi-rs napi-rs/napi-rs#2517.

For example, https://github.com/sxzz/ast-explorer uses @oxc-parser/wasm/web directly from CDN and that's not possible out-of-the-box with napi-rs output (though probably it's still possible by patching the js output during build on our own).

[Boshen]

For example, https://github.com/sxzz/ast-explorer uses @oxc-parser/wasm/web directly from CDN and that's not possible out-of-the-box with napi-rs output (though probably it's still possible by patching the js output during build on our own).

Sad to say that using from CDN is no longer supported :-(