terpstra-209 fixes a production build blind spot

The fork restores the type information the frontend needs from the backend, preventing a deployment-time failure.

infrastructure

This is a small but practical reliability fix for teams deploying the application through its container setup. The frontend can again see the shared descriptions of data coming from the backend, so production builds no longer fail when those references are checked.

The change also keeps the frontend and backend more tightly linked during the build process. That solves the immediate deployment issue, though a cleaner long-term approach would give both sides a dedicated shared source for those definitions.

So what Teams running this application in production should care because it removes a build failure that could otherwise block a release.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from terpstra-209/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
68719b5c fix(build): build frontend image from repo root so backend type imports resolve terpstra-209 2026-08-24 ↗ GitHub
commit body
frontend/src/app/components/shared/types.ts reaches into ../../../../../backend
for shared types. Building with context: ./frontend never had backend/ in the
image, so those imports silently degraded to any and next build failed on the
first implicit-any it hit. Build from repo root and mirror the layout instead.
LOCAL PATCH (not upstream).

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1414.md from inside the repo you want the changes in.

⬇ Download capture-thread-1414.md