-
Notifications
You must be signed in to change notification settings - Fork 49
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
SWC plugin #150
Comments
I’m here for it. Sounds necessary for me |
Yeah, I believe we should invest into it! I've been following SWC since the beginning and I'm glad that they finally got plugins system delivered and documented at least something. However, even in the doc they warn us:
So I'm not sure what direction to take. If you are leaning towards any of those approaches, I'd be happy to know why and happy to discuss next steps. |
This is pressing for me because: I've got a few nextjs projects in prod that would be using SWC already if not for pug. However, I'm hesitant about any solution because: It sounds like JS support is still up-in-the-air, and babel plugins may even be usable with SWC: swc-project/swc#2175 (comment) |
Next.js 11.1 (August 11th 2021 ) feature:
Rust-based Tooling: SWC integration to replace JS tooling (Babel and Terser).
What about new plugin?
The text was updated successfully, but these errors were encountered: