feat: generate TypeScript types after sync and init

[angeloashmore]

Resolves:

Description

Automatically generates prismicio-types.d.ts using prismic-ts-codegen after syncing models from Prismic. This runs after both sync (including watch mode) and init, so type definitions stay in sync with remote content models without a separate manual step.

Checklist

• A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

How to QA ¹

---

Note

Medium Risk
Automatically writing prismicio-types.d.ts after model sync adds a new side effect that can overwrite local type definitions and may impact projects with custom type generation workflows.

Overview
After prismic init and prismic sync, the CLI now auto-generates prismicio-types.d.ts from the freshly synced remote Custom Type and Slice models using prismic-ts-codegen.

In sync --watch, type generation is also re-run whenever remote model changes are detected, via a new shared generateAndWriteTypes helper.

^{Written by Cursor Bugbot for commit 8982265. This will update automatically on new commits. Configure here.}

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Duplicated type regeneration logic across two files

Low Severity

The inline code in init.ts that calls framework.getSlices(), framework.getCustomTypes(), framework.getProjectRoot(), and then generateAndWriteTypes() is an exact duplicate of the regenerateTypes function in sync.ts. If the codegen behavior ever needs to change (e.g., different options, added error handling), both locations need updating, and forgetting one would introduce a bug. The regenerateTypes helper could live in codegen.ts and be shared.

Additional Locations (1)

• src/commands/sync.ts#L262-L272

 

[cursor]

Hash updates before codegen prevents retry on failure

Medium Severity

In the watch loop, lastRemoteSlicesHash and lastRemoteCustomTypesHash are updated (lines 140, 145) before regenerateTypes runs (line 149). If regenerateTypes throws, the error is caught by the outer catch, but the hashes are already committed. On the next poll, remote hashes match the stored hashes, so no changes are detected — the codegen is never retried for those changes. The prismicio-types.d.ts file remains stale until an entirely new remote change occurs.