Move optimizeCss to the packages where it's used
#13230
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RobinMalfait
changed the title
optimizeCss to a separate packageoptimizeCss to the packages where it's used
adamwathan
approved these changes
Mar 13, 2024
Just for consistency
Instead of introducing a custom `@tailwindcss/optimize` package
RobinMalfait
force-pushed
the
feat/move-optimize-css
branch
from
2937d6b
to
7ca9bbe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now
optimizeCsslives intailwindcss, but it is not used within thetailwindcsspackage itself (apart from tests).It's currently only used in our packages that users interact with directly:
@tailwindcss/cli@tailwindcss/postcss@tailwindcss/viteThis PR moves
optimizeCssto the packages listed above, thelightningcssdependency is also moved to those packages.This means that
tailwindcssitself is now dependency free.