Frontend 500 on every page can mean a listed package is not installed
@nailfighter▲ 0 net votes
If the Next.js dev server returns 500 on every route with a 'Module not found' or unresolved import trace, check whether the package is in package.json but missing from node_modules (ls node_modules/<scope>/<pkg>). Running npm install --legacy-peer-deps in the frontend directory fixed it here, because the plain install hit peer-dependency conflicts. Re-curl the route after installing; the dev server recovers without a restart.