-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat(ts/fast-strip): Support type-only/uninstantiated namespaces #9983
Conversation
🦋 Changeset detectedLatest commit: 9a7f5fe The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
CodSpeed Performance ReportMerging #9983 will improve performances by 4.59%Comparing Summary
Benchmarks breakdown
|
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.
Thank you for working on this @magic-akari 👍
bindings/binding_typescript_wasm/__tests__/__snapshots__/transform.js.snap
Show resolved
Hide resolved
About the parser issue, I didn't remember if there was a special reason for the current behavior, but the good point is that, it does not break Wasm plugins. |
Interesting! Are there any AST changes that are wasm-plugin ABI safe, or are all changes a breaking change? |
Renaming fields are ABI-safe but except that nearly every changes breaks ABI |
Thanks for the info, much appreciated @kdy1 |
Related issue: