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 Support? #309
Comments
I imagine this would be considered once the feature is out of beta in NextJS, but also watching this as well! |
What do you mean out of beta? We're in Next 12 now and SWC support was introduced in Next 11. |
Because according to the docs, it's considered an Experimental feature: https://nextjs.org/docs/advanced-features/compiler#experimental-features |
We are still not using next-pwa in most of our apps because it doesn't support SWC and throws hundreds of yarn warnings about workbox, webpack, etc etc. |
I haven't experienced any blockers with next-pwa and SWC. The only packages that still request babel are cypress and the usual suspect: storybook. In case you're interested in my setup: https://github.com/pixelass/pwa-template |
Cypress 😢 Have an alternative? We'd gladly switch 😀 |
Cypress has their own process so it shouldn't impact you in any way. Babel is not even listed in the dependencies of the example repo I posted. It will be installed by cypress and storybook if you are using either but there is zero impact on the rest of the project (AFAIK). What I wanted to say is: "next-pwa does not have any noticable issues with SWC". I'm not sure if this has changed since this issue was opened, but from my experience this is currently a non-issue. |
Summary
Are there any plans on upgrading to SWC?
The text was updated successfully, but these errors were encountered: