Publish wasm

[Boshen]

No description provided.

[sxzz]

Hi, I would like to know if there is a reason to close this issue. Are there any plans to release wasm version?

[Boshen]

Hi, I would like to know if there is a reason to close this issue. Are there any plans to release wasm version?

I haven't found the time to properly maintain the wasm version. What's your usecase?

[sxzz]

I'd like to add Oxc parser to my AST Explorer

[0xdevalias]

I noticed that the playground's package.json loads it as such:

• https://github.com/oxc-project/oxc/blob/main/website/package.json#L32C5-L32C19
  • "@oxc/wasm-web": "link:../npm/wasm-web",

Yet there doesn't seem to be a npm/wasm-web in the main repo?

• https://github.com/oxc-project/oxc/tree/main/npm

Edit: Actually, I see now, it's the package.json has scripts to build it:

• https://github.com/oxc-project/oxc/blob/main/website/package.json#L8-L10
  • "wasm-dev": "wasm-pack build --out-dir ../../npm/wasm-web --target web --dev --scope oxc ../crates/oxc_wasm",
  • "wasm-build": "wasm-pack build --out-dir ../../npm/wasm-web --target web --release --scope oxc ../crates/oxc_wasm"
• https://github.com/oxc-project/oxc/tree/main/crates/oxc_wasm

[0xdevalias]

What's your usecase?

@Boshen We were also exploring whether it would be a suitable parser in wakaru (cc // @pionxzh):

• Performance improvement and potential tools to adopt pionxzh/wakaru#35 (comment)
• Performance improvement and potential tools to adopt pionxzh/wakaru#35 (comment)

I haven't found the time to properly maintain the wasm version

@Boshen Off the top of your head, what are the current issues with it that require further maintenance/etc? Do you consider it not up to date/usable/etc?

[Boshen]

What's your usecase?

@Boshen We were also exploring whether it would be a suitable parser in wakaru (cc // @pionxzh):

• Split code and save progress? pionxzh/wakaru#35 (comment)
• Split code and save progress? pionxzh/wakaru#35 (comment)

I haven't found the time to properly maintain the wasm version

@Boshen Off the top of your head, what are the current issues with it that require further maintenance/etc? Do you consider it not up to date/usable/etc?

Things could work if you intend to write everything in Rust, otherwise it's not going to work on the JS side. We lack all the things you need on the JS side after looking at your requirements.

[pionxzh]

We will need the wasm binding for js parser and the AST query and run them on JS side.

So the main blocker is that there is no enough resources and maintainers for wasm version?

[Boshen]

We will need the wasm binding for js parser and the AST query and run them on JS side.

So the main blocker is that there is no enough resources and maintainers for wasm version?

AST query and run them on JS side

We don't have a AST visitor on the JS side.

So the main blocker is that there is no enough resources and maintainers for wasm version?

Kind of, it's gonna be a lot harder to maintain because there are currently no TypeScript types for the AST on the JS side.

[magic-akari]

We don't have a AST visitor on the JS side.

Is using a WASM plugin a good idea?

[Boshen]

To be honest I'm still not sure whether the scope of this project should expand to supporting wasm and napi ...

[taosx]

While I appreciate the effort to keep the scope focused, I believe the oxc ecosystem could benefit from supporting multiple use cases with its components. That way it would attract new contributors and potentially alleviate some of the maintenance burden. This would also be advantageous for the community, as it would eliminate the need to duplicate efforts in developing lexers, parsers, traversers, etc.

In my case, I'm working on rewriting some JS/TS, from both internal JS and external systems (over network). oxc came to mind as a potential solution.

[Boshen]

Done! https://www.npmjs.com/package/@oxc-parser/wasm

I used wasm-pack build --target web for the build, probably need something like https://github.com/nshen/vite-plugin-wasm-pack to get it working with vite, otherwise vite will load the wasm file as a HTML file causing a CompileError: WebAssembly.instantiate(): expected magic word error.

[sxzz]

Thanks for your excellent work! However, the usage of docs may be wrong.

parseSync(code, { filename: "test.ts" });
> Error: expected instance of ParserOptions

The parser options cannot be a plain object.

---

If we pass a class, there's an error once get/set value.

const parserOptions = new ParserOptions()
parserOptions.filename = options?.filename || 'foo.ts'
> Error: null pointer passed to rust

[Boshen]

@sxzz I released @oxc-parser/wasm@0.0.4 and updated the README https://www.npmjs.com/package/@oxc-parser/wasm

wasm FFI is really confusing, I'm still unsure whether I fixed it or not, but "it works on my machine" at least.

[sxzz]

Great, it works now.

P.S. Oxc parser is already supported by my AST Explorer version.