Shift with red gradient lettering

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.

Using the Tailwind 1.x Shift to automatically upgrade your project has an estimated time savings of 4 hours.

Screenshot of a pull request with atomic commits for each change of the Tailwind 1.x Shift

Watch a demo

Requirements

  • A project running Tailwind 0.x.

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.json for Tailwind 1.x.
  • Renaming tailwind.js to tailwind.config.js.
  • Restructuring your Tailwind config file.
  • Replacing @tailwind preflight with @tailwind base.
  • Converting config() calls to theme().

Additional Upgrades

In addition to the Core Upgrades, the Tailwind 1.x Shift automates the 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 on the Pull Request to help guide any additional upgrade steps.

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. 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.