nextjs - 💡(How to fix) Fix Css translate rotate scale properties not output in css bundle if used before transform [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#86509Fetched 2026-04-08 02:10:32
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
commented ×2comment_deleted ×1issue_type_added ×1labeled ×1

Fix Action

Fix / Workaround

If we write css like below:

.element{
      rotate: 90deg;
      transform: skewY(7deg);  
      translate: 0% 100%; 
    }

Then the css bundle removes all individual transformation properties written before transform property and all those transformation properties written after transform property are merged into the transform property appended in order. This is not expected and breaks transformation order as per css.

Expectation is that the properties are retained as they were written and not processed any further. It was working correctly till NextJS@15 but on upgrade to version 16 this issue arose.

Code Example

.element{
      rotate: 90deg;
      transform: skewY(7deg);  
      translate: 0% 100%; 
    }

---

Operating System:
   Platform: Windows 10
Binaries:
   Node: 20.18.0
   npm: 11.4.2
   NextJS: 16.0.3
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/Samael-TLB/

To Reproduce

If we write css like below:

.element{
      rotate: 90deg;
      transform: skewY(7deg);  
      translate: 0% 100%; 
    }

Then the css bundle removes all individual transformation properties written before transform property and all those transformation properties written after transform property are merged into the transform property appended in order. This is not expected and breaks transformation order as per css.

Current vs. Expected behavior

Expectation is that the properties are retained as they were written and not processed any further. It was working correctly till NextJS@15 but on upgrade to version 16 this issue arose.

Provide environment information

Operating System:
   Platform: Windows 10
Binaries:
   Node: 20.18.0
   npm: 11.4.2
   NextJS: 16.0.3

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

CSS

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

next dev (local), next build (local), next start (local), Vercel (Deployed)

Additional context

No response

extent analysis

TL;DR

The issue can be fixed by reordering the CSS transformation properties to ensure that the transform property is declared last.

Guidance

  • Verify that the issue is specific to NextJS version 16 by testing the same CSS code in a NextJS 15 environment to confirm the regression.
  • Check the CSS bundle output to confirm that the transformation properties are being merged into the transform property.
  • Consider reordering the CSS transformation properties to ensure that the transform property is declared last, like so:
.element{
  translate: 0% 100%; 
  rotate: 90deg;
  transform: skewY(7deg);  
}
  • If reordering is not feasible, investigate alternative solutions such as using a separate CSS class for each transformation property or using a different CSS bundling approach.

Notes

The issue appears to be specific to NextJS version 16, and the exact cause is unclear without further investigation. The proposed solution is based on the assumption that the issue is related to the order of the transformation properties.

Recommendation

Apply workaround: Reorder the CSS transformation properties to ensure that the transform property is declared last, as this is a non-invasive change that can potentially resolve the issue without requiring a version upgrade or significant code changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Css translate rotate scale properties not output in css bundle if used before transform [2 comments, 2 participants]