How lttb/taddy works
Main Components
a. Core Engine Layer:
• NameGenerator and static processing components
• Rule injection system (RuleInjector)
b. Framework Integration Layer:
• Next.js (@taddy/next-plugin)
• Vite (@taddy/vite-plugin)
• ESBuild (@taddy/esbuild-plugin)
• React Native support
• Vue integration
• Various framework examples (Astro, Nuxt, SvelteKit, etc.)
c. Build System Layer:
• Babel plugin system (@taddy/babel-plugin)
• Macro processing (taddy.macro)
• Compilation and optimization pipeline
Component Relationships
• Data flow from style definitions to processed CSS
• Compilation process flow
• Framework integration paths
• Runtime vs. build-time processes
Specific Implementation Details
a. Style Processing Pipeline:
Style Definition → Babel Transform → Static Optimization → CSS Generation → Injection
b. Framework Integration Points:
• How each framework plugin connects to the core
• Different entry points (macro, direct usage, plugin)
Key Technical Elements
• CSS rule injection system
• Static optimization engine
• Framework-specific transformers
• Development tools (playground, documentation)
Architecture Patterns
Highlight:
• Plugin architecture
• Framework adaptation layer
• Build-time optimization
• Runtime style injection