Automatic Splitting

Splitting stops being a build-time optimization and becomes a natural outcome of Maple’s demand-driven architecture.

With Maple, you effectively get the most aggressive form of splitting possible without configuring a single chunking strategy. If a component is not on the screen, its styling cost is zero.

• Styles for unseen routes are never generated
• Styles for unused components never exist
• Styles behind feature flags or conditionals are skipped entirely
• Styles for dynamic content are generated only when needed

There is no need to align CSS chunks with JavaScript chunks, no route-based extraction, and no risk of overfetching styles “just in case.”