15:32:47.007
+ First Load JS shared by all 226 kB
15:32:47.007
├ chunks/061943c7-6604cff26105a688.js 36.7 kB
15:32:47.007
├ chunks/9059-7e68d68d0290cdc2.js 117 kB
15:32:47.008
├ chunks/d288ded8-850c7a7b59c024dc.js 66.1 kB
15:32:47.008
└ other shared chunks (total) 6.13 kB
15:32:47.008
15:32:47.008
15:32:47.008
ƒ Middleware 94.2 kB
15:32:47.008
15:32:47.009
○ (Static) prerendered as static content
15:32:47.009
◐ (Partial Prerender) prerendered as static HTML with dynamic server-streamed content
15:32:47.010
ƒ (Dynamic) server-rendered on demand
15:32:47.010
15:32:47.573
Traced Next.js server files in: 124.489ms
15:32:48.770
Created all serverless functions in: 1.196s
15:32:48.913
Collected static files (public/, static/, .next/static): 27.661ms
15:32:49.494
Build Completed in /vercel/output [8m]
15:32:49.909
Deploying outputs...
An unexpected error happened when running this build. We have been notified of the problem. If you have any questions, please contact Vercel Support https://vercel.com/help
It looks like one of your routes is being generated with too long of a path name, I have DM’d you with the route in question just to keep it private
This is a current internal limitation of experimental_ppr and will hopefully be either fixed or documented before the stable release
@jacobparis is there any thread is going on for follow up on this ?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.