Skip to content

chore: parse using oxc instead of typescript, and move ts to dev deps#38

Open
eMerzh wants to merge 1 commit intohudochenkov:mainfrom
eMerzh:oxc_parser
Open

chore: parse using oxc instead of typescript, and move ts to dev deps#38
eMerzh wants to merge 1 commit intohudochenkov:mainfrom
eMerzh:oxc_parser

Conversation

@eMerzh
Copy link
Copy Markdown

@eMerzh eMerzh commented Apr 21, 2026

I was a bit sad that ts was used as running dep,

so i wonder if we couldn't use oxc to parse instead of TS, this should improve speed quite a bit, and reduce deps weight as well ....

hope this can inspire / get integrated or else :)

@hudochenkov
Copy link
Copy Markdown
Owner

Interesting idea!

The dependency weight is indeed much smaller (24.4MB → 3.6MB).

  1. We need to see benchmarks comparing existing parser and oxs-parser for our use case.
  2. How TypeScript written in Go (7.0 beta) compares with oxc? Again, benchmarks are needed. Because this project will use TypeScript, written in Go, when it's available.
  3. While TypeScript has bigger size, there is a huge possibility that it's already present in project's node_modules, unlike oxc-parser. So the size point might be not relevant.
  4. Snapshots in tests are changes, which might indicate a bug with using new parser.

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