Skip to content

Optimize generated CSS output #14873

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RobinMalfait merged 7 commits into from
Nov 6, 2024
Merged

Optimize generated CSS output #14873

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
1a1a9ba
run Lightning CSS twice
RobinMalfait Nov 5, 2024
9ecfcb0
update tests
RobinMalfait Nov 5, 2024
d262870
bump lightningcss to the latest version
RobinMalfait Nov 5, 2024
f93e6bc
update changelog
RobinMalfait Nov 5, 2024
53b6aff
comment why we run `optimize` twice
RobinMalfait Nov 6, 2024
b0972d8
adjust changelog entry
RobinMalfait Nov 6, 2024
774290e
Update CHANGELOG.md
RobinMalfait Nov 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
comment why we run optimize twice
  • Loading branch information
@RobinMalfait
RobinMalfait committed Nov 6, 2024
commit 53b6aff30cfc40632a1927641199b8216f53e5fa
2 changes: 2 additions & 0 deletions packages/@tailwindcss-cli/src/commands/build/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -431,5 +431,7 @@ function optimizeCss(
}).code
}

// Running Lightning CSS twice to ensure that adjacent rules are merged after
// nesting is applied. This creates a more optimized output.
return optimize(optimize(Buffer.from(input))).toString()
}
2 changes: 2 additions & 0 deletions packages/@tailwindcss-postcss/src/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,6 +239,8 @@ function optimizeCss(
}).code
}

// Running Lightning CSS twice to ensure that adjacent rules are merged after
// nesting is applied. This creates a more optimized output.
return optimize(optimize(Buffer.from(input))).toString()
}

Expand Down
2 changes: 2 additions & 0 deletions packages/@tailwindcss-vite/src/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,6 +298,8 @@ function optimizeCss(
}).code
}

// Running Lightning CSS twice to ensure that adjacent rules are merged after
// nesting is applied. This creates a more optimized output.
return optimize(optimize(Buffer.from(input))).toString()
Copy link
Contributor

@philipp-spiess philipp-spiess Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we can get away with running optimize just once if lightningcss is configured as the CSS processor... It might have a different config so probably not 😬

Copy link
Member Author

@RobinMalfait RobinMalfait Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that's tricky. Our config sets Safari to a version that doesn't understand nesting yet.

One suggestion that Devon had was to put @media queries on the outside instead of nested to do the merging, but the current change is a bit easier especially once Lightning CSS can handle this natively.

}

Expand Down
2 changes: 2 additions & 0 deletions packages/tailwindcss/src/test-utils/run.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,5 +36,7 @@ export function optimizeCss(
}).code
}

// Running Lightning CSS twice to ensure that adjacent rules are merged after
// nesting is applied. This creates a more optimized output.
return optimize(optimize(Buffer.from(input))).toString()
}