Docs
Changelog
Latest updates and announcements around the Astro registry, docs shell, and component release work.
June 10, 2026
CLI file-update prompts and preview flags
The motion-blocks CLI now asks before overwriting existing files, supports read-only diff and view previews, and never hangs in CI.
This release focused on making the CLI safe to run inside existing projects. Rather than silently clobbering files, it pauses and asks — or skips automatically in non-interactive environments.
What changed
- Per-file write decisions — before any existing file is changed, the CLI shows a diff and asks whether to overwrite, skip, or keep. New files are always created without a prompt.
motion-blocks initconfirmation — re-running init on a project that already hasmotion-blocks.jsonasks before overwriting; declining skips the config write but lets the rest of init continue.- Patch prompts — tsconfig and vite.config patches now show the planned change and ask for confirmation before applying. Declining prints the equivalent manual step.
--yesflag — auto-confirms the dependency install prompt without affecting per-file overwrite safety.--diff [path]and--view [path]— read-only preview flags formotion-blocks add; nothing is written, no prompts are shown.- CI safety — non-interactive environments (piped stdin, no TTY) default to skipping conflicting files instead of hanging. Pass
--overwriteto override. - Outcome summary — after
motion-blocks addfinishes, a count shows how many files were created, updated, skipped, or identical. - React support —
initvite patcher now handles React projects;addpatches JSX custom-element types on React targets. - CLI 0.0.2 — package version bumped with full npm metadata (homepage, repository, bugs, keywords).
Why it matters
Running the CLI a second time used to risk losing local edits. The per-file prompt model removes that risk: you stay in control of every change, and the outcome summary tells you exactly what happened. CI pipelines get the same safety without needing extra flags.
June 10, 2026
Deeper published registry item module
Docs catalog, preview registration, and nav ordering now derive from published registry item metadata — manual seed lists and hand-edited import lists are gone.
This release removes a class of maintenance work that grew with every new registry item. Adding a component previously required updating the docs catalog seed, the preview element import list, and the navigation ordering by hand. Those three surfaces now derive from a single published item interface.
What changed
- Docs catalog from registry metadata — the component index, sidebar, and detail pages all pull from the published registry item list instead of a separate hand-maintained seed. Grouping, ordering, and hidden-lib filtering come from registry source data.
- Preview registration from
elementsmetadata —component-preview-scripts.astrono longer contains a long hand-edited import list. Custom element modules are registered based on each published item’selementsfield, including supporting elements for multi-element items. - Prev/next navigation aligned with catalog order — previous and next links on detail pages use the same ordered published item list as the catalog, so navigation and browsing order cannot drift apart.
- Build-time drift validation —
registry:build:checknow catches: missingcomponent.json, item included in source registry without a manifest, published item without a demo partial, missing preview registration metadata, invalid docs ordering values, and orphaned catalog entries. Each failure names the item and the missing piece. - Package path consolidation — the CLI package moved from
motion-blocks-clitomotion-blocksacross root scripts,README.md,RELEASE.md, and build paths.
Why it matters
Publishing a new registry item now means: write the Web Component, write component.json, include it in the composed source registry, add a demo. Everything else — catalog placement, preview wiring, navigation — follows automatically. Missing any piece produces a named build failure rather than a silent gap in the docs.