Test the download, not just the demo

A preview can look correct while the exported package is missing the files that make it work.

A component library has two products: the browsing experience and the files users take away.

Automated checks should open the standalone HTML, inspect the ZIP manifest, capture console errors, and exercise keyboard paths.

When customization changes tokens, the exported CSS must contain those exact values.

A practical test

Open the standalone export, disconnect the network, and use the component with a keyboard. If the core experience breaks, the preview was hiding a dependency.

Browse validated components