For the complete documentation index, see llms.txt. Prefer markdown by appending.mdto documentation URLs or sendingAccept: text/markdown.
Updates
Upstream Edge Kit updates, local changes, merge conflicts, and verification before publishing your updated product.
Your upstream remote connects the product to future Edge Kit improvements. Merge those changes with your own features and configuration, then verify the resulting app before releasing it.
With the Cloudflare GitHub integration connected, you can review the update on a PR preview before merging it into your production branch.
CLI updates
With a clean working tree, run npx @turbostarter/cli@latest project update. The CLI checks your kit and upstream, then merges the latest changes. The steps below cover a manual update.
Local changes
Commit your current work or stash it before updating:
git stashKeep track of whether you created a stash so you can restore it after the merge.
Upstream
Merge the latest changes and install the updated dependencies:
git pull upstream main
pnpm installChoose merging rather than rebasing if Git asks for a strategy.
Conflicts
Combine upstream improvements with your own product changes. Pay particular attention to resource configuration, translations, plans, routes, and newly required environment values.
Keep your production identifiers and branding while accepting new configuration required by the update. For lockfile conflicts, resolve the manifest changes first and regenerate the lockfile with pnpm install rather than editing dependency entries by hand.
If you stashed work, restore it after resolving the upstream merge:
git stash applyResolve any remaining conflicts before checking the app.
Verification
Regenerate derived output and run the project's checks:
pnpm cf-typegen
pnpm generate-routes
pnpm format:fix
pnpm lint
pnpm testLint includes type checking. Run the build after changes to routes, server rendering, or content.
Database migrations
Apply new migrations locally before testing the updated app. Production migrations run during deployment, so review them alongside your release.
Publication
Commit the verified update and push it to your product's repository. Follow deployment for a production release and check the customer flows affected by the update.
How is this guide?
Last updated on
Dependencies
Install, update, and remove Edge Kit packages with pnpm, check their Worker runtime requirements, and validate dependency changes before deployment.
Environment variables
How Edge Kit loads and validates configuration. Secrets in .env.local, public VITE_ values, wrangler.jsonc vars, and envin validation.