Skip to content
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.

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

Inline @import rules in tailwindcss/index.css at publish time for better performance #13233

Merged
merged 9 commits into from
Mar 13, 2024

Conversation

RobinMalfait
Copy link
Member

This way none of the tools using @import "tailwindcss"; have to resolve imports at "runtime" because it will already be inlined when it's published.

This does increase the bundle size of the tailwindcss package, but it's still going to be a very small package.

This implementation is fairly simple right now, because we don't have
to worry about resolving folders or modules since we don't use them.
CHANGELOG.md Outdated Show resolved Hide resolved
RobinMalfait and others added 3 commits March 13, 2024 21:40
Co-authored-by: Jordan Pittman <jordan@cryptica.me>
Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
@RobinMalfait RobinMalfait merged commit 9fc5aa1 into next Mar 13, 2024
1 check passed
@RobinMalfait RobinMalfait deleted the feat/inline-css-at-build-time branch March 13, 2024 21:26
@RobinMalfait RobinMalfait changed the title Inline the tailwindcss/index.css contents at publish time Inline @import rules in tailwindcss/index.css at publish time for better performance Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants