You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Primary focus of @swc/core is transform interface, which is a consolidated pipeline across various SWC's feature. Which means, SWC already have various sub-features to make it work and some are partially enabled, and some are not enabled cleanly.
Recently I did casual chat with kdy that if we could expose those more cleanly, can be used across ecosystems for the SWC and javascript. Namely, these are the features (I can think of) SWC can provide or already provide. Possibly there'll be some more I don't recall though.
Ecma parser : available via parse()
Ecma codegen (from ast): available via print()
HTML parser
CSS parser / codegen
If you tried to use an available feature (parse / print) over other well-known (acorns, babel..) and decide not to use: what was the major blocker?
If you'd like to have unavailable, what you would like to get / why / what other details you'd like to have?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Context: https://twitter.com/_ojkwon/status/1683222663697940480
Primary focus of
@swc/core
istransform
interface, which is a consolidated pipeline across various SWC's feature. Which means, SWC already have various sub-features to make it work and some are partially enabled, and some are not enabled cleanly.Recently I did casual chat with kdy that if we could expose those more cleanly, can be used across ecosystems for the SWC and javascript. Namely, these are the features (I can think of) SWC can provide or already provide. Possibly there'll be some more I don't recall though.
parse()
print()
Beta Was this translation helpful? Give feedback.
All reactions