-
Notifications
You must be signed in to change notification settings - Fork 1
feat: transpile typescript code instead of transform #60
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
base: main
Are you sure you want to change the base?
Conversation
commit: |
Intresting. Have you comparared oxidase with oxc-transform? The former is more actively maintained and is from original author. /cc @Boshen |
Yes, maintainer activity is one of my primary considerations when choosing a replacement. Our use case is quite special: we can’t provide sufficient context to transformers, so they often inadvertently modify our code. For example, even replacing quotes can cause issues. We need to avoid any optimizations introduced by transformers entirely.
Given these reasons, |
|
@Boshen Is the another project some kind of transpiler? I know our use case is niche, but it's pity that oxidase is no longer maintained. I tried If we want to strip these keywords accurately, we need to call TypeScript's scanner, which is not much different from @danielroe What do you think about switching to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I make a lib with oxc-parser
for transpiling https://github.com/Teages/oxc-blank-space
It passed all test from ts-blank-space
and enum test from oxidase
(ts-blank-space
does not support enum).
I haven't done any bench yet, because the performance improve may be not obvious before we migrate to rust. But I think this would be a good start for switching to "transpile".
esbuild
with oxidase
TODO:
<template>