Summary
Neither the frontend nor the backend has any error-tracking/APM integration — no Sentry (or equivalent), and no CHANGELOG.md tracking what's shipped. For a project working toward launch, production errors currently have no tracking beyond console/log output.
Location
frontend/package.json, backend/package.json — no @sentry/* or equivalent error-tracking package in either.
Problem
Once this app has real users, an unhandled exception or a spike in a specific error type has no automated way to surface to the team — it would only be noticed if someone happened to be tailing logs, or a user reported it manually. This is a significant gap for a project explicitly working toward being launch-ready.
Impact
Medium-high as a pre-launch readiness item: production observability for errors is currently a blind spot.
Acceptance Criteria
Suggested Approach
Sentry has first-party SDKs for both Next.js (@sentry/nextjs) and Express (@sentry/node) with straightforward setup guides — this is likely the path of least resistance rather than building custom error-tracking.
Summary
Neither the frontend nor the backend has any error-tracking/APM integration — no Sentry (or equivalent), and no CHANGELOG.md tracking what's shipped. For a project working toward launch, production errors currently have no tracking beyond console/log output.
Location
frontend/package.json,backend/package.json— no@sentry/*or equivalent error-tracking package in either.Problem
Once this app has real users, an unhandled exception or a spike in a specific error type has no automated way to surface to the team — it would only be noticed if someone happened to be tailing logs, or a user reported it manually. This is a significant gap for a project explicitly working toward being launch-ready.
Impact
Medium-high as a pre-launch readiness item: production observability for errors is currently a blind spot.
Acceptance Criteria
frontend/andbackend/Suggested Approach
Sentry has first-party SDKs for both Next.js (
@sentry/nextjs) and Express (@sentry/node) with straightforward setup guides — this is likely the path of least resistance rather than building custom error-tracking.