build(frontend): migrate CRA to Next.js (CSR lift-and-shift) #21

2026-07-12T01:09:16+02:00

cesnimda commented

2026-07-12 01:09:16 +02:00

Wave 6: CRA to Next.js migration, static export, CSR lift-and-shift (no App Router rewrite). See commit message for full detail.

cesnimda added 1 commit 2026-07-12 01:09:16 +02:00

build(frontend): migrate CRA to Next.js (CSR lift-and-shift)

CI and Deploy / test (pull_request) Failing after 50s

Details

CI and Deploy / deploy (pull_request) Has been skipped

Details

acf60c2a07

Wave 6. Swaps react-scripts' build/dev tooling for Next.js while
keeping the app's actual routing/rendering model unchanged -- the app
is almost entirely behind auth with no proven SSR/SEO need, so a real
App Router rewrite would touch ~90 files for zero user-visible benefit.

- next.config.js: output:'export' (static HTML+JS, same "single
  index.html served by nginx with try_files fallback" deploy as CRA).
- app/layout.tsx + app/page.tsx: root shell ports public/index.html's
  <head>, mounts the whole existing App tree client-only (ssr:false)
  since it reads window/localStorage during initial render and Next's
  static prerender would otherwise execute that on the server.
- Renamed src/pages/ -> src/views/ (Next's Pages Router auto-detects
  any `pages/` dir under the app root and tried to build our React
  Router page components as its own routes).
- REACT_APP_* -> NEXT_PUBLIC_* across code, .env.development,
  Dockerfile, docker-compose.yml build args.
- Replaced the CRA SVGR import (`ReactComponent` from .svg, unsupported
  under Turbopack) with a small inline JobbjaktMark component.
- TypeScript 4.9 -> 5.9 (MUI v8's type-checked build needs syntax
  4.9's parser rejects; CRA never hit this because babel doesn't
  type-check).
- Dropped CRA-only files (index.tsx, reportWebVitals, react-app-env.d.ts,
  public/index.html); kept react-scripts as the Jest test runner only
  (next/jest migration not needed -- the existing config already works).

Verified: `next build` static export succeeds, `next dev` serves the
landing page and client-side routes (login etc.) correctly, all 57
frontend tests + 172 backend tests still green.

Known caveat: deep-linking straight to a sub-route (e.g. /login) 404s
in `next dev` since there's no server route for it -- the app only
ever mounts at "/". Production is unaffected: nginx's existing
try_files fallback still serves index.html for any path.

cesnimda added 1 commit 2026-07-12 01:22:20 +02:00

fix(frontend): relax npm peer-dep resolution for react-scripts vs TS 5.9

CI and Deploy / test (pull_request) Successful in 2m6s

Details

CI and Deploy / deploy (pull_request) Has been skipped

Details

dbb15804a3

CI's npm ci (strict peer resolution) rejected the TypeScript 5.9 bump
from the Next.js migration: react-scripts still declares typescript
^3.2.1||^4 as a peer. Local `npm install` didn't catch this -- it
resolves peer conflicts leniently by default; only `npm ci` enforces
them. react-scripts is kept solely as the Jest test runner now (it
doesn't type-check), so relaxing this one peer constraint is safe.

cesnimda merged commit 8a9e402baa into main

2026-07-12 01:25:23 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cesnimda/jobtrackingapp#21