Files
ditto.site/CHANGELOG.md
T
Michael ColeandClaude Opus 4.8 638a0516c5 Add ditto unpack CLI to turn clone result JSON into a project tree
The REST API returns a clone as a giant `files` map JSON blob with no
first-party way to use it — users were left staring at kilobytes of
escaped JSON with no path from "you got JSON" to "here's a project".

Add packages/cli: a zero-dependency `ditto` CLI whose `unpack` command
walks the files{} map from POST /v1/clones (or GET .../result) and
writes a real project tree to disk:

- text files written from inline content;
- binary assets materialized from inline base64, else fetched from their
  reference URL using $DITTO_API_URL / $DITTO_API_KEY (--no-fetch writes
  just the text tree and lists skipped assets);
- path-traversal guards (clone results are untrusted) and sha256
  integrity checks;
- reads JSON from stdin ("-") so a curl response pipes straight in;
- clear errors for queued jobs with no files yet, and a tip pointing at
  the /bundle endpoint when assets can't be fetched.

Document the pipe-from-curl one-liner prominently next to the REST
examples in README.md and docs/SERVICE.md, add a package README, a
Repository Map row, a root `unpack` script, and a CHANGELOG entry.
Covered by 9 tests (text tree, stdin, inline base64, live URL fetch with
auth + relative-URL resolution, --no-fetch, traversal refusal, queued-job
detection, sha256 mismatch).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-01 15:40:28 -04:00

3.5 KiB
Raw Blame History

Changelog

All notable changes to this project are documented here. The format is based on Keep a Changelog; this project is pre-1.0, so minor/patch semantics are not yet guaranteed.

[Unreleased]

Added — ditto unpack CLI

  • packages/cli — a zero-dependency ditto command-line helper. ditto unpack <clone.json|-> <out-dir> turns the files map returned by POST /v1/clones (or GET /v1/clones/:id/result) into a real project tree on disk: text files written inline, binary assets materialized from inline base64 or fetched from their reference URL ($DITTO_API_URL / $DITTO_API_KEY), with path-traversal guards and sha256 integrity checks. Reads from stdin so a curl response can be piped straight in. Documented next to the REST examples in the README and docs/SERVICE.md.

Added — Open-source readiness

  • Added support, release, responsible-use, CODEOWNERS, and gitattributes files.
  • Made workspace package metadata explicit for license and repository scanners.
  • Tightened contributor and PR checklists around runtime audit, documentation, responsible use, and committed artifacts.

Changed — Generated app dependency templates

  • Updated generated Next apps to the current Next 15 line with React 19.
  • Updated generated Vite apps to Vite 6.4 with React 19, keeping the generated app Node floor compatible with the repo's >=20 engine policy.

Added — Service layer (REST + MCP API)

A hosted service around the deterministic compiler, as an npm-workspaces monorepo (packages/*). The compiler's clone behavior is unchanged — only a library boundary was added.

  • packages/core — the sole compiler adapter: runCloneJob (temp-dir lifecycle, optional verify), collectFileMap, cacheKey.
  • packages/db — Drizzle schema + migrations (jobs/clones/cache/apiKeys), repo, and a pg-boss queue.
  • packages/storageArtifactStore (local disk or S3/R2 via presigned URLs), deterministic tgz/zip bundles.
  • packages/api — Hono app: REST routes + MCP (Streamable-HTTP), API-key auth, rate limiting, and SSRF protection.
  • packages/worker — queue consumer with isolated per-worker verify build harness; supports multi-page (clone_site) jobs.
  • Freshness-bounded caching (CACHE_STALE_AFTER, noCache), Docker images + docker-compose (Postgres + MinIO), CI, and Railway/Neon/R2 deploy docs.
  • Root CLI passthrough scripts so the compiler CLI runs from the repo root too.

See docs/SERVICE.md and README.md.

Changed — Component extraction keeps styling out of the content model

  • Extracted components no longer pull per-instance className strings into the editable content model (content.ts). When a node's class varies across instances, the tokens common to all instances are baked into the component skeleton and only the per-instance diff is emitted — to a separate _styles.ts plumbing module (alongside _cids.ts), merged back at render time with a generated cn() helper. content.ts now holds only semantic fields (text, href, src, alt, …). Render-identical (token order doesn't affect computed style); gates 06 and site/determinism unaffected. Swap cn for tailwind-merge if you want conflict-aware merging when hand-editing the overrides.

Notes

  • The deterministic compiler predates this changelog; the current architecture is summarized in README.md, with operational service details in docs/SERVICE.md.