Replies: 6 comments 8 replies
-
@davidczachor I'm not sure what's been causing this but you may want to try redeploying a few times and clearing out caches, I've had the same issue with the rc since it isn't exactly stable but it seems to have cleared up on it's own, also are you using any experimental features? |
Beta Was this translation helpful? Give feedback.
-
@davidczachor did you fix this? im facing the same problem here |
Beta Was this translation helpful? Give feedback.
-
I'm having the same problem as well. Seems like it might somehow be caused by forcing static rendering. If I remove |
Beta Was this translation helpful? Give feedback.
-
I'm having the same exact problem, haven't found a way to make the build work in the Vercel deployment. |
Beta Was this translation helpful? Give feedback.
-
same error here, works when removing experimental ppr |
Beta Was this translation helpful? Give feedback.
-
This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community |
Beta Was this translation helpful? Give feedback.
-
Summary
`
○ (Static) prerendered as static content
ƒ (Dynamic) server-rendered on demand
Traced Next.js server files in: 36.218ms
Created all serverless functions in: 1.833s
Collected static files (public/, static/, .next/static): 3.248ms
Error: ENOENT: no such file or directory, open '/vercel/path0/.next/server/app/index.rsc'
This is my error I am getting deploying to Vercel. I am on Next 15-rc and locally it builds and startings without issues.
Example
No response
Steps to Reproduce
Here is my repo if you would like to try and running it on Vercel:
https://github.com/davidczachor/czachor-ca
Beta Was this translation helpful? Give feedback.
All reactions