Preview and export introduced two different ways to experience generated source. Both were designed around explicit limits.
The export path packages a completed run as source, a validated manifest, handoff guidance, GitHub-ready metadata, and a gitignore helper. It is created in memory and rejects unsupported paths, secret-bearing categories, missing files, and inconsistent manifests. The package tells its recipient to review and test the application instead of presenting setup notes as proof of production readiness.
The running preview path is even narrower. It accepts a small literal JSX and plain CSS subset, constructs an inline artifact, and places it in a sandbox without same-origin access, network, storage, forms, or remote resources. Components, hooks, event handlers, general expressions, and full Tailwind compilation are outside that first runtime.
An unsupported application remains visibly unsupported. PrettyBaby returns diagnostics instead of silently substituting a fake preview or deployment result. The preview's ability to say no is part of the product's transparency.
← Back to PrettyBaby