The Tailwind UI Shift automates the changes for upgrading from Tailwind UI 1.x to Tailwind UI 2.x. Using the Tailwind UI Shift to automatically upgrade your project has an estimated time savings of 1 hour.
The Tailwind UI Shift does not include all changes for upgrading to Tailwind 2.x. You should run the Tailwind 2.x Shift first, or implement the changes in the Tailwind Upgrade Guide.
The Tailwind UI Shift automates many of the changes for upgrading Tailwind UI for Tailwind CSS 2.x, including:
@tailwindcss/ui
plugin.max-content
and min-content
utilities.form-*
elements.focus
with ring
utilities.package.json
for Tailwind UI.There are some upgrades the Tailwind UI Shift can not perform automatically. When Shift detects these it adds a detailed comment on the Pull Request to help guide any additional upgrade steps.
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. If you are not using a Tailwind configuration file and have a complex project structure, you may configure Shift with your project paths.
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.