Course lesson 11 · Building in a Mono Repo
Deploy your changes!
This short checkpoint deploys the now data-backed user application and verifies its link operations against D1. The instructor demonstrates reading a build error rather than postponing deployment until the entire course is finished. Continuous deployment checkpoints help isolate problems to a small set of recent changes.
Primary source: course video 11 · Supplied English subtitles · 00:04:28.
Understand the idea
- The existing deploy script still handles building assets and publishing the application; new functionality does not require a new deployment mechanism.
- The project’s build checks can block deployment before upload when source issues such as unused variables are found.
- The deployment output lists the D1 binding, connecting configuration review to the running app.
- The hosted application can behave differently from the experimental remote local-development setup, so both need practical verification.
What the course does
- Stop the local user application and run its deployment script.
- Read the reported unused state-setter error in the unfinished socket component, and correct the intentionally unused destructuring slot.
- Run deployment again and inspect the uploaded assets and listed D1 binding.
- Open the deployed URL and test the links list, link editor, and a country destination update.
- Refresh the page to confirm those changes persist in the database-backed application before moving to the data service.
Watch for
- The unused-variable example depends on the exact starter and local code state; it may not appear in your checkout.
- Added advice: fix the reported source problem rather than removing useful build checks simply to make deployment pass.
- Authentication is still implemented later in the course, so this checkpoint should not be mistaken for a completed production application.
Recall before revealing
What does deploying at this checkpoint validate beyond seeing the local page work?
Reveal the explanation
It validates the application build, deployment configuration, hosted D1 binding, and actual link operations in the Cloudflare environment.
Try it
Deploy your current course application and perform one persistent edit through the hosted interface.
Check your result
The deployment succeeds, the expected D1 binding appears, and the edit survives a full reload.
Practice prompts and answer checks are added teaching material. Answer from memory first, then compare and explain any difference.
Rewatch only what you need
Open this lesson in your original course library and seek to the times below. Videos are not hosted on this site.
- 00:00:00 — Why deploy incrementally
- 00:01:00 — Run deploy and inspect its failure
- 00:02:00 — Fix the unused placeholder variable
- 00:03:00 — Verify the deployed database-backed UI
Companion primary documentation: Drizzle with Cloudflare D1. For recorded API names, commands, limits, and prices, check the version you use.