mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
7b19b00b57
If you have a PostCSS config file, that is not simple (has functions, requires, ...). In that case we don't migrate the PostCSS file. Because we don't migrate, the `didMigrate` is still false and we continue with the next migration. The issue here is that there are 2 states encoded in the same variable and they should be two separate variables because there is a difference between: 1. Not finding a file at all 2. Finding a file, but not migrating it Before this change, the output looks like this if you have a complex PostCSS file: ``` │ Migrating PostCSS configuration… │ The PostCSS config contains dynamic JavaScript and can not be automatically migrated. │ No PostCSS config found, skipping migration. ``` After this change, the output looks like this: ``` │ Migrating PostCSS configuration… │ ↳ The PostCSS config contains dynamic JavaScript and can not be automatically migrated. ``` Also updated the output to include `↳ ` to be consistent with the other logs.
A utility-first CSS framework for rapidly building custom user interfaces.
Documentation
For full documentation, visit tailwindcss.com.
Community
For help, discussion about best practices, or any other conversation that would benefit from being searchable:
Discuss Tailwind CSS on GitHub
For chatting with others using the framework:
Join the Tailwind CSS Discord Server
Contributing
If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.