The contents for this repository pertaining to the @toolwind/upgrade tool can be found here.

A custom Tailwind CSS v3 → v4 upgrade tool focused only on migrating utility classes.

This tool assists in upgrading Tailwind CSS v3 projects to v4 by scanning for utility classes and updating them based on a provided Tailwind configuration file.

This is a fork of the official @tailwindcss/upgrade package, with some key differentiators, listed below.

Unlike the original Tailwind upgrade tool, this version only migrates utility classes. It does not attempt to migrate Tailwind or PostCSS configurations, or automatically install or update any dependencies.

• 🎯  Focus on Utility Classes
  This tool exclusively targets the migration of Tailwind CSS utility classes found based on your configuration or provided inputs.


• 🛡️  Zero Side Effects
  This tool focuses solely on utility class migration, with…
  
  
  • ⛔️  No Config Changes
    Your tailwind.config.js and related configuration files remain untouched.
  
  
  • 📦  No Package Updates
    Dependencies like tailwindcss, @tailwindcss/postcss, and plugins like autoprefixer are left for you to manage as you see fit. See the official upgrade guide.
  
  
• 🧩  Flexible Input
  
  
  • ⚙️  Config Files
    Use --config (-c) to specify paths or glob patterns to match one or more configuration files.
  
  
  • 🔍  Custom Source Patterns
    Use the --source (-s) flag to override the content array and specify exact file paths or glob patterns to scan for utilities.
  
  
  • 💻  Direct String Migration
    Use the --inline-source (-i) flag to migrate a string containing utility classes directly from the command line without scanning files.
  
  

This tool excels in more complex setups and codebases where you'd need to update utility classes across project directories based on one or more Tailwind configuration files, especially in: This could be monorepos, multi-X applications, even databases (we've seen it).

This tool excels in more complex scenarios where you'd need to update utility classes across various areas in your app based on one or more Tailwind configuration files, especially in:

• Monorepos: Easily migrate codebases with multiple projects, each having its own tailwind.config.js, by using glob patterns with the --config flag, enabling batch migrations.
• Targeted migrations: Focus only on utility class changes without altering configuration files or dependencies, allowing for more controlled upgrades.
• CI/CD & scripting: Integrate utility class migration into automated workflows.
• Utility classes stored in databases: I've seen it.

You can run the tool using npx @toolwind/upgrade [OPTIONS]:

# Basic usage with a single config file
npx @toolwind/upgrade --config 'path/to/tailwind.config.js'

# Basic usage with multiple config files (using glob)
# ⚠️ IMPORTANT: Always quote glob patterns in your shell!
npx @toolwind/upgrade --config '**/tailwind.config.{js,ts,cjs}'

# Override template file scanning locations (ignores config's `content` array)
# ⚠️ IMPORTANT: Always quote glob patterns in your shell!
npx @toolwind/upgrade --config <config_path> --source 'src/**/*.html' 'app/**/*.tsx'

# Migrate a string of utility classes directly (outputs to console)
npx @toolwind/upgrade --config <config_path> --inline-source '<div class="bg-blue-500 hover:!bg-red-600">...</div>'

# Migrate a string, specifying the source type (e.g., for Pug, Haml parsing)
npx @toolwind/upgrade --config <config_path> --inline-source 'button.bg-blue-500 Click' -x pug

While this tool aims to be accurate, automated code migration can sometimes produce unexpected results, especially in complex scenarios like JavaScript/TypeScript files where utility classes might be constructed dynamically or embedded within template literals, or where JS looks like Tailwind utility classes to the parser (e.g. () => !hidden && result → ❌ () => hidden! && result).

Always review the changes made by this tool carefully before committing them. Verify that the migrated utilities function as expected in your application's context.

Feel free to contribute by opening issues or submitting pull requests on GitHub. Any contributions that help improve this tool and make the Tailwind CSS v4 migration process smoother for everyone are welcome.