Course lesson 02 · Getting Started
Setting up the project
The starter is a pnpm monorepo containing two applications and one reusable package. The lesson gets the existing interface running, establishing the build order and the relationship between root convenience scripts and scripts inside each workspace package. The visible dashboard is still mostly a scaffold with dummy data, so a working page does not yet mean the backend features exist.
Primary source: course video 02 · Supplied English subtitles · 00:07:31.
Understand the idea
- An apps directory groups independently deployable services; a packages directory groups code those services reuse.
- Each application has its own source and package.json, while the root provides workspace-wide commands.
- The Data Ops package must be built into its dist output before applications can consume the exported JavaScript and types.
- pnpm filtering selects a workspace by its package name; entering its directory and running its local script is another way to work on the same app.
What the course does
- Fork the starter into your GitHub account and clone that fork so later changes and deployment integration belong to your repository.
- Inspect apps/user-application, apps/data-service, and the Data Ops package before changing code.
- Install workspace dependencies with pnpm, then run the root helper that builds the shared package.
- Start the frontend using the root filtered helper or run its dev script from the application directory.
- Open the local interface on port 3000 and inspect the marketing page, dashboard, link editor, and placeholder analytics.
Watch for
- A number of dashboard values, maps, and editor behaviors are dummy implementations at this point.
- Added advice: read the actual package.json script names rather than reconstructing hyphens from spoken subtitles.
Recall before revealing
Why build Data Ops before starting an application that imports it?
Reveal the explanation
The application consumes the package’s exported build output; the build creates the JavaScript and type files at those export paths.
Try it
In a separate course checkout, identify the workspace package names, build the shared package, and start the user application.
Check your result
The dashboard opens locally, and you can point to the scripts and package that produced it.
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 — Fork and clone the starter
- 00:01:00 — Monorepo structure
- 00:03:00 — Build the Data Ops package
- 00:04:01 — Root scripts versus app-local scripts
Companion primary documentation: Cloudflare Workers runtime APIs. For recorded API names, commands, limits, and prices, check the version you use.