Strange error with npm run build

[TomasErikssonDev]

Summary

Hello, I started last month with a new nextjs project and it worked fine til I added another .ts-file with useEffect in a hook-function and then it work in dev mode but not when I build:

Error occurred prerendering page "/xxx". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of undefined (reading '__NEXT_PRIVATE_MINIMIZE_MACRO_FALSE')

This doesn't solve it
'use client';
export const dynamic = 'force-dynamic';

Why is the error so obfuscated? Why does an useEffect makes the difference..?

If I dig in the minified code I find this:
return Q.env.__NEXT_PRIVATE_MINIMIZE_MACRO_FALSE&&(0,p.useEffect)(()=>{r&&(e?ee(n,

I'm not so experienced with NextJS, but the problem seems ridiculous hard to solve.

Kind regards
Tomas

Additional information

No response

Example

No response

[CoderDeltaLAN]

Context

• Next.js 14.x
• Node 18/20
• Command: npm run build
• Error: TypeError: Cannot read properties of undefined (reading '__NEXT_PRIVATE_MINIMIZE_MACRO_FALSE')

Cause
This usually appears when:

• A file with use client or hooks is mixed in the wrong layer (e.g. imported by a server component).
• Stale build artifacts (.next, node_modules) or lockfile drift.
• Minification / SWC cache issues during the production build.

Fix (minimum viable)

1. Clean and reinstall:

   rm -rf .next node_modules
   rm -f package-lock.json
   npm ci

2. Make sure the component using useEffect is:
   • A client component (top of the file: use client)
   • Not imported by a server component directly.
3. Typecheck before build:

   npx tsc --noEmit

   This often catches imports that only break in prod.
4. Rebuild with a clean env:

   NEXT_TELEMETRY_DISABLED=1 npm run build

5. If still failing, clear SWC/native cache:

   rm -rf node_modules/.cache
   npm rebuild

6. Last resort: set the page to dynamic to avoid prerender mismatch:

   export const dynamic = 'force-dynamic';

Notes

• Docs: Pre-rendering errors
• Absolute imports / alias config: https://nextjs.org/docs/app/building-your-application/configuring/absolute-imports-and-module-aliases
• If this solves it, please Mark as answer so others can find it.