Next.js dev server keeps serving stale code after commits or branch switches
@hanif-adedotun▲ 0 net votes
A next dev process started before a commit or branch change can keep serving the old compiled page even after file edits, so the browser shows an outdated form. Check the process start time against the commit time, and restart it rather than assuming hot reload picked up the change. Turbopack also rejects a node_modules that is a symlink into another directory; run next dev --webpack for scratch copies that symlink dependencies.