Where did turbo.useSwcCss go? #78296
-
|
Where did turbo.useSwcCss go? We need it! In Next v14, This prevents us from launching Next.js applications using Turbopack after updating to Next.js v15—Turbopack has become useless due to the removal of this feature. So, what I want to know is, what happened? Why was Can we get |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Maintaining a CSS compiler is a lot of work and we thought it would be better for the community to team up with the LightningCSS team. Our experience has been that most times people have felt blocked from using LightningCSS we were able to suggest a relatively simple way of rewriting their code to achieve their goals. I realize that may not be the case for you though. The first step would be raise that issue in the LightningCSS repo. This issue might be a good place to start. I'll leave this discussion open for now so people can link to issues opened in the LightningCSS repo, so we can track true blockers to Next.js users. |
Beta Was this translation helpful? Give feedback.
-
|
It feels like an AI-generated response; you clearly don't understand what I'm saying. |
Beta Was this translation helpful? Give feedback.
-
|
Not an AI generated response, just trying to be polite. Perhaps you're not understanding because I didn't share enough context. SWC's CSS compiler was always experimental and we were the ones building it. Perhaps it worked for your use case, but there was a lot of work left to do to make it stable and then keep maintaining it and we felt it was the best decision to contribute to LightningCSS instead. Calling us arrogant for this choice is not going to persuade us to pick it back up again. We would like to help people who are struggling to adopt LightningCSS, but we can't do that without specific examples. |
Beta Was this translation helpful? Give feedback.
Maintaining a CSS compiler is a lot of work and we thought it would be better for the community to team up with the LightningCSS team.
Our experience has been that most times people have felt blocked from using LightningCSS we were able to suggest a relatively simple way of rewriting their code to achieve their goals. I realize that may not be the case for you though. The first step would be raise that issue in the LightningCSS repo. This issue might be a good place to start.
I'll leave this discussion open for now so people can link to issues opened in the LightningCSS repo, so we can track true blockers to Next.js users.