Upgrade Tailwind 0.x to Tailwind 1.x
The Tailwind 1.x Shift automates the upgrade of your project from Tailwind 0.x to Tailwind 1.x. This includes all of the changes listed in the Tailwind Upgrade Guide.
This includes upgrading your Tailwind configuration file, replacing utility class references, adopting the new color palette, and much more.
Using the Tailwind 1.x Shift to automatically upgrade your Tailwind project has an estimated time savings of 4 hours.
Watch a demo
Requirements
- Running Tailwind 0.x (configurable for any project).
Core Upgrades
The Tailwind 1.x Shift automates many of the upgrades listed in the Tailwind Upgrade Guide, including:
- Removing instances of old Tailwind utility classes.
- Converting old Tailwind utility classes.
- Bumping
package.jsonfor Tailwind 1.x. - Renaming
tailwind.jstotailwind.config.js. - Restructuring your Tailwind config file.
- Replacing
@tailwind preflightwith@tailwind base. - Converting
config()calls totheme().
Additional Upgrades
In addition to the Core Upgrades, the Tailwind 1.x Shift automates optional upgrades listed in the Tailwind Upgrade Guide, including:
- Styling any heading elements with font size, weight, and leading utilities.
- Adding the new Tailwind 1.x utilities to any list elements.
- Adopting the new Tailwind 1.x color palette (configurable).
- Moving your customizations under the new
theme.extend. - Optimizing your Tailwind config file.
Manual Upgrades
There are some upgrades the Tailwind 1.x Shift can not perform automatically. When Shift detects these it adds a detailed comment to the Pull Request to guide any additional steps you may need to do manually.
Custom Configuration
By default, Shift will look for the Tailwind config file to determine your project path. This will be used as the base path when searching for additional assets and templates.
When not specified, Shift will assume a Laravel project structure. If you are not using a Tailwind configuration file or have a different project structure, you may configure Shift for your project.