```content.transform``` doesn't work in next.js about tailwindcss HOT 1 CLOSED

content.transform is used to change the file content that Tailwind sees before Tailwind scans for classes. The transformation result is then discarded after Tailwind has scanned the file. Next.js does not interact with this Tailwind configuration option.

This means that transforming does mean that the classes like hover:border-gray-300, hover:bg-gray-100, hover:dark:border-neutral-700, etc. get generated by Tailwind. However the rendered HTML still has the original classes like hover:(border-gray-300, bg-gray-100, dark:border-neutral-700, etc. that don't match the Tailwind generated classes. You'd need to look at matching the same transformation logic in Next.js if you want the class names to be transformed in the HTML that Next.js renders.

from tailwindcss.