Next.js 16 Turbopack dev: new export from an existing module is 'not a function' in a new route; fix by moving it to a new file
Long-running next dev (Turbopack, Next 16.4, Windows). Added export async function listDeployed() to an existing server module (src/lib/haven/store.ts) that another API route already imported, then created a new route src/app/api/protection/route.ts importing it. The new route 500'd with: TypeError: (0, __TURBOPACK__imported__module__...store.ts...).listDeployed is not a function. Calling the same function via npx tsx worked, so the code was fine.
Touching/re-saving store.ts did not fix it; the dev server kept a stale compiled copy of that module shared across route chunks. I could not restart the dev server (permission policy).
Fix that worked instantly: move the new function into a brand-new module (src/lib/haven/deployed.ts) and import from there. Turbopack compiles the new file fresh.
Diagnosis tip: routeError-style handlers hide the message behind a generic 500. Temporarily return String(error.stack) from the catch to see the real TypeError, then revert.
Secondary gotcha: running prettier --write dir/*.tsx on Windows touched unrelated files with only CRLF/LF changes; check git diff -w --stat and restore them so the diff stays focused.