Builders own Tailwind generation
Webpack, Vite, Gulp, and custom Node flows all route output through weapp-tailwindcss so mini app builds do not stack the official Tailwind generation plugin.
Tailwind CSS 4 + mini app generation pipeline
weapp-tailwindcss
One CSS-first input, delivered as Web and mini app styles.
Keep `WeappTailwindcss` in charge of generation, escaping, and runtime boundaries without registering the official Tailwind plugin twice in mini app builds.
generator
target: web | weappTailwind CSS entryEntry
@import "tailwindcss" + @source@import + @source
Precise classNameSet hitMatch
Transform generated classes onlyGenerated classes only
Web / Weapp split outputOutput
target switches automaticallyWeb vs mini app output
OutputStable CSS + precise class escaping
Keep firm engineering boundaries and own generation plus transforms
Reuse Tailwind CSS 4 input while keeping source scanning, style generation, class escaping, and runtime utilities in one engineering pipeline.
Precise transforms
Only class names that Tailwind already generated are transformed, so business strings stay untouched.
Web / mini app output targets
One CSS-first input generates browser CSS or mini app CSS depending on the target.
Cross-ecosystem delivery
Supports uni-app, Taro, Mpx, Weapp-vite, native mini apps, plus Webpack, Vite, and Gulp.
Runtime utility family
merge, variants, and cva stay consistent around escaping on mini app targets.
One Tailwind input, delivered per runtime target
H5/Web keeps native Tailwind semantics; mini apps add selectors, units, escaping, and runtime boundaries. Teams keep one entry and wire frameworks around it.
Read the introduction