What problem does it solve?
It guides developers who maintain a self-built bundler, adapter, or advanced asset pipeline to integrate weapp-tailwindcss correctly, covering compiler sessions, module graphs, watch/HMR invalidation, source maps, and subpackage style isolation without misusing output-directory scanning.
Core Features & Use Cases
- Core Compiler Integration: Design
createCompiler() lifecycles with root sessions, immutable snapshots, revisions, and precise invalidate() handling for watch and HMR.
- Bundler Adapter Patterns: Apply shared graph-mode timing for Vite, Webpack, Rspack, Gulp, Rollup, and Rolldown adapters while keeping module graphs and asset write-back in the bundler.
- Style Injection & Subpackage Isolation: Configure
weapp-style-injector and per-scope Tailwind entries so main, normal, and independent subpackages keep isolated style assets.
- Use Case: A team building an in-house mini-program bundler uses this Skill to wire Tailwind CSS generation, template/JS transforms, and HMR invalidation into their own module graph.
Quick Start
Ask the assistant to design a custom bundler integration for weapp-tailwindcss using the Core API with watch and subpackage style injection support.