Open alex-cory opened 2 years ago
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
Because according to the docs, it's considered an Experimental feature: https://nextjs.org/docs/advanced-features/compiler#experimental-features
Version | Notes |
---|---|
v13.0.0 | SWC Minifier enabled by default. |
v12.3.0 | SWC Minifier stable. |
v12.2.0 | SWC Plugins experimental support added. |
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
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 😢 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?