Upgrading

Packs are copied into your repository, the same way shadcn/ui works. You own the files. That means upgrades are merges, not invisible package bumps.

What `stack.json` tracks

stack.json at the project root records:

App paths (backend, frontend, admin when present)
Installed pack ids
Deploy targets and services (after you run deploy)

The CLI uses it to know what is already installed and what infrastructure already exists. Commit it. It is configuration, not a secret store.

Pack and template updates

A license includes 12 months of CLI downloads. During that window you can re-run:

bash

npx @hype-stack/cli compose
# or
npx @hype-stack/cli template <name>

Because the files are already yours, a re-install can overwrite local edits. Treat updates like vendored code:

Commit your project first
Re-run the CLI for the packs you want refreshed
Diff and merge carefully
Run migrations if schema changed
Typecheck and test before deploying

When the download window ends you keep everything already in the repo. You renew only if you want further catalog updates. See pricing.

Dependency bumps

Root and app package.json files are yours. Bump React, Hono, Prisma, and the rest the way you would in any monorepo:

bash

pnpm update
pnpm typecheck
pnpm test

Watch Prisma major upgrades: regenerate the client and re-run migrations. Watch HyperFetch / Hono type changes: the frontend SDK is derived from the backend app type.

Agent rules and skills

If you scaffolded with editor rules, newer CLI versions may ship improved rules. Re-running create/compose with the same --editor flags can refresh them; diff before keeping changes so you do not lose custom rules you added.

What does not auto-update

Copied pack source
Codemod results already applied to your routes and nav
Your theme tokens and landing pages

That is intentional. The trade-off for owning the code is that improvements arrive when you pull them.

What is Hype Stack for the ownership model
Compose and Template
Migrations

Development