The Tailwind 2.x Shift automates the upgrade of your project from Tailwind 1.x to Tailwind 2.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 2.x Shift to automatically upgrade your project has an estimated time savings of 4 hours.
The Tailwind 2.x Shift automates many of the upgrades listed in the Tailwind Upgrade Guide, including:
package.jsonfor Tailwind 2.x.
screensto new variants.
In addition to the Core Upgrades, the Tailwind 2.x Shift automates optional upgrades listed in the Tailwind Upgrade Guide, including:
There are some upgrades the Tailwind 2.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.
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.
Sign in with any of the following services to connect Shift with your Laravel project.
Don't use one of these services?
Temporarily push your project to a free, private repository on one of these cloud-based services or upgrade your project locally with Shift for Docker.