grit sync — Go to TypeScript

One command, one purpose: keep the TypeScript types in sync with the Go structs. grit sync reads every model and re-writes packages/shared/src/types/. Run it any time the API shape changes.

What it does

$grit sync

You'll see:

✓ Read 5 models from apps/api/internal/models/
✓ Wrote packages/shared/src/types/user.ts
✓ Wrote packages/shared/src/types/product.ts
✓ Wrote packages/shared/src/types/index.ts
✓ Wrote packages/shared/src/schemas/user.ts (Zod inferred from struct tags)
✓ 5 types in sync.

Why it matters

Without sync, every time you add a field to a Go struct you also have to remember to add it to the TS type. That's how schema drift happens — your API returns is_active but the frontend types still say it doesn't exist, so VS Code says "property does not exist" while the data IS being sent.

With sync, you change Go once and run one command. TS picks up the new field. Build errors point you at every place to update.

When to run it

• After every grit generate resource ...
• After you manually edit a Go struct
• After you pull from main and someone else changed models
• In CI before pnpm build

What it doesn't do

Sync handles the shape — the TS type matches the Go struct. It doesn't handle behaviour — e.g., custom validation rules, derived fields, or computed properties. Those still need manual work in the Zod schema.

You've finished chapter 4

Generate writes 8 files; sync keeps the types aligned. Together they let you add a resource to a Grit project in under a minute. The chapter assignment — generate an Order + an OrderItem + sync — is waiting in the sidebar.

What's next

Chapter 5 — the last chapter. We zoom out from individual resources and talk about the 5 architecture modes and how to pick the right one for your idea.