Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experiment with typescript-go instead of @swc/wasm-typescript #200

Open
trivikr opened this issue Mar 11, 2025 · 3 comments
Open

Experiment with typescript-go instead of @swc/wasm-typescript #200

trivikr opened this issue Mar 11, 2025 · 3 comments

Comments

@trivikr
Copy link
Member

trivikr commented Mar 11, 2025

Is your feature request related to a problem? Please describe.

Not a problem, but TypeScript team just announced today (Tue, March 11) that they're going to port TypeScript to Native, and their port shows 10X improvement.

This module currently uses @swc/wasm-typescript, a WebAssembly port of the SWC TypeScript parser.
Switching to official TypeScript port might improve reliability, and possibly performance

Describe the solution you'd like

Evaluate migrating from @swc/wasm-typescript to typescript-go
Even if the experiment if unsuccessful, report the findings back to the project https://github.com/microsoft/typescript-go/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen

@marco-ippolito
Copy link
Member

marco-ippolito commented Mar 11, 2025

No blank spacing so its not possible until that is supported. I don't think its worth trying

@marco-ippolito
Copy link
Member

I created a feature request in typescript for this microsoft/TypeScript#61410

@JounQin
Copy link

JounQin commented Mar 12, 2025

Or why not use napi-rs as wrapper but WASM now?

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

No branches or pull requests

3 participants