What problem does it solve?
Upgrading an existing weapp-tailwindcss project to the current v5/Tailwind CSS 4 toolchain involves removing legacy patches, outdated CLI workflows, and duplicate Tailwind generators, which is error-prone when done manually.
Core Features & Use Cases
- Legacy Cleanup: Removes old
weapp-tw patch postinstall hooks, deprecated tailwindcss-patch dependencies, duplicate PostCSS/Vite Tailwind plugins, and Webpack 4-only entries.
- CLI Migration: Moves projects from old
@weapp-tailwindcss/cli 3.x/4.x alpha workflows (init, Sass/Less, directory scanning) to the standalone 5.x CLI with explicit bundler integration.
- Entry & Plugin Rebuild: Converts Tailwind entries to pure CSS with absolute
cssEntries and registers the current Vite, Webpack 5, Rspack, or Gulp plugin per target platform.
- Use Case: A uni-app project still running
weapp-tw patch on postinstall and the old CLI init flow can be migrated step-by-step to v5, with verification of mini-program safe selectors, H5 output, and HMR updates.
Quick Start
Use the weapp-tailwindcss-migrate skill to upgrade my legacy weapp-tailwindcss project to the current v5 Tailwind CSS 4 setup and remove the old patch and CLI configuration.