Turbopack removes styles from TailwindCSS/DaisyUI

[iKushiu]

Link to the code that reproduces this issue

https://github.com/iKushiu/turbopack-bug

To Reproduce

1. Start the application in dev mode with Turbopack active (next dev --turbopack)

Current vs. Expected behavior

When the application is started with turbopack some styles from DaisyUI are removed.

But it should look like this

If you start it without turbopack the styles are normal.
The Problem occurs in 15.4.1 in 15.4.0 the styles are normal too.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Thu Jun  5 18:30:46 UTC 2025
  Available memory (MB): 15451
  Available CPU cores: 16
Binaries:
  Node: 18.19.1
  npm: 9.2.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.4.1 // Latest available version is detected (15.4.1).
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

_PACK-5139

[dotNomad]

I noticed a similar issue when using writing-mode: vertical-rl; alongside spacing and border utilities like space-x-<number> or border-x in Tailwind. --turbopack influenced the output CSS.

On an element with writing-vertical-rl border-x classes I get two different outputs for border-x

With next dev --turbopack:

.border-x {
    border-inline-style: var(--tw-border-style);
    border-left-width: 1px;
    border-right-width: 1px;
}

Just next dev:

.border-x {
    border-inline-style: var(--tw-border-style);
    border-inline-width: 1px;
}

With next start:

.border-x {
    border-inline-style: var(--tw-border-style);
    border-inline-width: 1px;
}

Edit: After a little bit more testing I learned the above doesn't appear to be an issue with Next.js 15.3.x even when using --turbopack, but does on 15.4.1

[razzeee]

Yeah, it was working correctly with 15.3.x and with 15.3.1-canary.11

[Faraz1995]

have similar issue on next js 15.4.3
remove padding in daisy ui
in turbo pack mode

[sedegah]

Also seeing this issue on 15.4.1 and up. With --turbopack, certain Tailwind and DaisyUI styles (like padding, borders, and some theme tokens) don't render as expected, but everything works fine without it or in 15.3.. Seems like Turbopack is interpreting some utility classes differently. Would be great to confirm if this is a regression or something in the CSS processing pipeline.

[DuckThom]

I also just ran into this issue, very confusing why Storybook and my production builds had the correct styling but dev mode didn't.
I've been checking older next releases and, for me, 15.4.0-canary.104 is working properly and it breaks when updating to 15.4.0-canary.105. (The reason 15.4.0 is working is because I think the published tag actually is one of the 15.3 releases)

So probably one of the changes here is responsible: https://github.com/vercel/next.js/compare/v15.4.0-canary.104..v15.4.0-canary.105

Unfortunately, I have no idea what exactly I'm looking for, so for now I'm stranded again but perhaps someone else can make something of this 😄

[heinsenberg82]

Also facing same issue

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[mischnic]

Probably #81075 then if the generated CSS is wrong/different

[Deroswent]

I have the same problems. up

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[youngdriversacademy]

Same issue here

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!