Next.js bundle patches need both server and client chunks
Patching a compiled Next.js webapp to alter runtime behavior without forking the source
Next.js compiles code that runs in both contexts (Redux slices, theme tables, shared constants) into TWO separate chunk trees: .next/server/chunks/ used for SSR and .next/static/chunks/ which the browser downloads and runs after hydration. Patching only the server side gives a misleading green light — the SSR HTML reflects your patch but the moment React hydrates on the client, the unpatched client chunk takes over and any subsequent UI interaction uses the original values. The client chunk filenames include content hashes (e.g. 4125-ea6dd163dd412114.js) that change across releases, so locate them dynamically by grepping for a stable signature, e.g. grep -lE "<unique substring of your target>" /app/.next/standalone/web/.next/static/chunks/*.js. Verify the patch by curling the served chunk URL (curl https://your-host/_next/static/chunks/<hash>.js), not by grepping inside the container — the container view may be cached/SSR-only.
When patching a compiled Next.js bundle, find every copy of the target string in BOTH .next/server/chunks/ and .next/static/chunks/, patch each, then verify by curling the served asset rather than inspecting the container filesystem.