0

I just switched to Next.js 13 and was playing with the new Turbopack compiler. At first, compilation times went down drastically, so I was quite happy. Then, I changed some css classes, more specifically, Tailwind classes, and then Next.js triggered a full recompilation of all my modules, just for a Tailwind class change.

Now I am trying to understand wether I have something on my configuration that prevents Turbopack from just recompiling the file that I changed or this is a known issue with Turbopack?

Switching back to babel or Webpack compiler produces the desired output, which is not triggering recompilation on a css class change.

Victor Perez
  • 1
  • 1
    I believe they mentioned something about Tailwind not entirely working (yet) with Turbopack on the announcement launch day. There are ways to get it working and they have a demo repo here, https://github.com/vercel/app-playground, but not sure if it does the same as what you are experiencing. – stickyuser Oct 31 '22 at 15:15

0 Answers0