3 ms·
One of the authors has contributed to SWC. I wonder what caused them to build an alternative.
by depr 3y ago
One of the authors has contributed to SWC. I wonder what caused them to build an alternative.
- the_mitsuhiko 3y agoI'm not sure how the projects ended up where they are, but Oxc which this relates to has a very specific vision of how to improve the experience for the JavaScript tooling ecosystem which I'm not sure SWC shares. https://oxc-project.github.io/docs/guide/introduction.html https://oxc-project.github.io/docs/guide/introduction.html I have used SWC internals recently for a toy project of mine and was generally let down a bit by some of the rather unwieldy internals, insufficient documentation and pretty hefty footprint.
- deleted 3y ago[deleted]
- no_wizard 3y agoIn many ways its not an alternative, in particular, SWC does not handle resolving and other bundler specific concerns, and dropped the concept of JS interop with plugins (its all rust built WASM now). I also blame Vercel, they have put zero investment in documenting SWC. The person behind the project used to be more prolific in documenting things, and that all stopped once Vercel scooped them and the project up for use in turbopack (which has not materialized as a standalone solution like they promised, funnily enough)
- ametrau 3y agoI would avoid anything by the company behind meteor.