There’s probably a simple explanation for this, but I’ve encountered this issue without any action on my part beyond clicking the “Deploy” button for this particular boilerplate on Vercel: Next.js App Router Playground. I have a Hobby account and have been able to successfully clone to my GitHub and deploy other boilerplates, so I’m surprised I am getting blocked here. The build logs seem identical to locally, and seem to be completing everything up until Deploying outputs...
, which will eventually fail after running for some 20-30minutes.
Traced Next.js server files in: 85.501ms
Created all serverless functions in: 351.664ms
Collected static files (public/, static/, .next/static): 15.216ms
Build Completed in /vercel/output [52s]
Deploying outputs...
Is this somehow an account specific issue, perhaps based in limitations for projects or deployments, or is it a dependency issue potentially? Is anyone else able to reproduce this issues for themselves?