Files
ditto.site/compiler
Samraaj BathandClaude Fable 5 199359d0a6 Wave 4: reveal settling + replay, 206/magic-byte media fix, hidden-geometry banding, bare-zero utility gating
Capture (4a):
- stabilize: dwell-scroll settling pass + known-library pre-reveal
  neutralization after lazy promotion, so every viewport snapshot records
  the post-reveal steady state (about-page sections no longer captured
  blanket-hidden: 24 base `invisible` wrappers -> 0)
- probeReveals: extended to the visibility + entrance-animation family;
  DittoMotion replays them (JS re-hide on mount, IntersectionObserver
  reveal, 4s force-reveal failsafe) so SSR/non-JS still shows content
- assets: 206 range-response bodies are no longer stored as full assets
  (full-fetch fallback) + video magic-byte validation - the about-page
  hero video is now a valid 6.0MB ftyp mp4 instead of 18.9KB of garbage

Generate (4b):
- css: hidden-node geometry policy - a visibility:hidden box with a 0x0
  captured bbox at a band becomes display:none there; an OCCUPYING hidden
  box gets the captured per-viewport geometry instead of the baked
  canonical one. Also covers the ancestor-hidden-at-base case (the
  cropin.com/cotton slider arrow: hide inherited from an elementor-widget
  ancestor at every width parked a desktop left:548px box inside a 375px
  viewport -> body.scrollWidth 585; now 375 on both verified pages)
- tailwind: bare-zero utility gating - font-size:0 -> text-[0px] and
  letter-spacing:0 -> tracking-[0px] (text-0/tracking-0 are silently
  invalid in Tailwind v4; fixes permanently-visible map labels on the
  cotton Global-presence section)

Verified: 87/87 compiler tests green, full-workspace suite green,
regenerated cropin.com + /cotton/ builds measure 375px scrollWidth at a
375px viewport, and a fresh /about/ clone renders all reveal sections
with scroll-replay against the live site.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-03 18:33:10 -07:00
..
2026-06-29 15:11:48 -07:00
2026-06-29 16:14:44 -07:00
2026-06-29 16:14:44 -07:00
2026-06-29 15:11:48 -07:00
2026-06-29 15:11:48 -07:00
2026-06-29 15:11:48 -07:00
2026-06-29 16:14:44 -07:00
2026-06-29 15:11:48 -07:00

ditto.site Compiler

This workspace contains the deterministic compiler used by ditto.site. It captures a source URL, builds a render IR, infers assets/fonts/tokens/sections/recipes/SEO, generates a Next.js App Router app by default or a Vite React app on request, and validates the result with deterministic gates.

The full architecture overview lives in ../README.md. This file keeps only compiler-local commands and notes.

Commands

cd compiler
npm install
npx playwright install chromium

npm run clone -- https://example.com/
npm run clone -- https://example.com/ --serve   # then npm install + npm run dev
npm run clone -- https://example.com/ --open    # ...and open the browser too
npm run clone -- https://example.com/ --mode=multi --styling=tailwind
npm run clone -- https://example.com/ --mode=single --framework=vite
npm run clone-site -- https://example.com/
npm run validate-site -- ../runs/site-example.com/<timestamp>
npm run clone -- https://example.com/ --mode=multi --concurrency=5
npm run clone -- https://example.com/ --mode=multi --validate --validate-concurrency=3 --viewport-concurrency=2
npm run validate-site -- ../runs/site-example.com/<timestamp> --validate-concurrency=3 --viewport-concurrency=2
npm run bench -- --tier=easy
npm run bench-site
npm run quality -- ../runs/example.com/<timestamp>
npm run audit -- ../runs/example.com/<timestamp>
npm test
npm run typecheck

Root-level scripts forward to these commands, so npm run clone -- <url> works from the repository root too.

("Clone" here = generating a codebase from a live URL, not git clone; no source repo required.) On success the CLI prints a copy-paste-safe summary: a single quoted cd … && npm install && npm run dev line plus safe-to-edit pointers. Pass --serve to run install + dev automatically, or --open to also launch the browser. Without --out, a runs/<site>/latest symlink always points at the newest run so paths aren't timestamp-fragile.

Multi-page generation defaults to the fast no-validation path. Use --validate when the clone command itself should run the full build/render/gates QA pass, or run validate-site separately. --concurrency controls source route capture; --validate-concurrency controls how many routes validation grades at once; and --viewport-concurrency controls how many clone viewports each route renders at once.

Generated App Shape

Default Next generated apps use src/app/ditto.css and optional helpers under src/app/ditto/. Vite generated apps use src/ditto.css and optional helpers under src/ditto/, with multi-route pages under src/routes/. Validation builds keep data-cid attributes for source/clone alignment; delivered apps strip those validation ids and keep only required data-ditto-id anchors.