One component. Seven dialects.
Prism generates a real, typed package per framework from one Lit source. Hand-written wrappers: zero.
What changed in v4.2.0.
Nine Items From Someone Building With It. Published August 22, 2026. All packages version together.
An application building two shells against 4.0.1 sent back eleven findings in one batch. Nine were ours. Every one was reachable in the first hour of using the library, none was subtle, and the suite — 4,694 tests at the time, with a mutation run behind it — caught none of them.
- A Closed Menu Put A Scrollbar On The Page
- Two Components That Ship Together, Broken When Composed
- The Shell Can Be Embedded
- Props And Docs That Described Something Else
- Toasts Can Be Driven Without A Reference
- Dev Warnings Say What You Are Looking At
- Seven Components' Console Noise, From One Line
- Wrappers: Bindings, Handles, And 140 Dead Imports
- One Thing That Can Stop Compiling
- What The Batch Says About The Tests
Yours, all the way down.
Override four tokens and every gradient, glow and focus ring follows. The utility classes read the same tokens, so your layout moves with them.
:root { --accent-primary: #4d7ef7; --accent-primary-rgb: 77, 126, 247; --accent-secondary: #9567ff; --accent-secondary-rgb: 149, 103, 255;}That file is the entire theme, applied to this page for real — compound tokens reference these four, so every gradient, glow and focus ring follows. Build yours →
272 utility classes and every component read the same tokens — spacing and radius here move only this card, exactly the way a scoped override would in your app. Utilities →
Every push runs the gauntlet.
The real CI gates on this repository, under their real names.
- Generated files match source 0 diffs
- Component tests 2465 tests
- SSR render check 189/189
- axe-core audit 0 serious
- Typecheck generated declarations every subpath
- Smoke-test packed tarballs every package
APG patterns, focus management and reduced motion are built per component. Accessibility →