Monorepo, pnpm, and Turborepo Build Context
Phase 32 objective: containerize the existing architecture without moving durable state, secrets, or business responsibilities into the container layer.
Challenge A monorepo image build needs workspace metadata, shared packages, lockfiles, and application source while still avoiding a giant context full of Git history and local node_modules. # .dockerignore essentials .git **/node_modules **/.next **/dist .env .env.* !*.env.example
TaskFlow approach Use the monorepo root as the build context. Maintain a strict .dockerignore. Install from pnpm-lock.yaml with --frozen-lockfile. Build the selected workspace and its dependency graph.
Pruning A future optimization may use turbo prune --docker to create a reduced workspace context. Phase 32 teaches the baseline first so pruning remains understandable rather than magical.
Monorepo pnpm and Turborepo Build Context matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Monorepo pnpm and Turborepo Build Context” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: route data → UI state → component tree → interaction → accessible feedback. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Dockerfiles and compose/dev verification that build and run TaskFlow services from clean inputs.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
if (query.isPending) return <TaskSkeleton />;
if (query.isError) return <TaskError retry={query.refetch} />;
if (!query.data.length) return <EmptyTasks />;
return <TaskTable tasks={query.data} />;Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Monorepo pnpm and Turborepo Build Context” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Build with frozen lockfile and inspect image layers/size.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Huge build context invalidating caches
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.