Vercel Build Fails The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. #3614
Replies: 4 comments
-
Did you figure this out? I'm having the same issue. |
Beta Was this translation helpful? Give feedback.
-
Nope, I tried for about 6 months and finally gave up. No one from the app
dev seems to respond either.
…On Thu, Dec 1, 2022 at 12:57 PM Stephen ***@***.***> wrote:
Did you figure this out? I'm having the same issue.
—
Reply to this email directly, view it on GitHub
<#3614 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWKWCYZGBPVC6JSSYO24GF3WLEGKTANCNFSM6AAAAAASRGVFAE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@REVREBEL I started over and then followed these settings, and it worked https://developer.cal.com/self-hosting/vercel Added the ENV variables and changed the settings with these parameters:
|
Beta Was this translation helpful? Give feedback.
-
I wasn't using calcom but perpetually got this exact error. This likely won't be a direct fix since calcom is wrapping your vercel deployment through Next env vars; but for what it's worth: I had to change my direct dependency |
Beta Was this translation helpful? Give feedback.
-
Found a bug? Please fill out the sections below. 👍
Issue Summary
A summary of the issue. This needs to be a clear detailed-rich summary.
Steps to Reproduce
Same issue as a previous ticket #1908
I tried this solution 'Their docs are not fitting for this repo, though. Needed to change the build command to cd ../.. && yarn run build and install command to yarn install --prefix=../..."; however, that didn't work either.
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Technical details
[00:29:50.842] Please check the following, and reach out to support if you cannot resolve the problem:
[00:29:50.842] 1. If present, be sure your
build
script in "package.json" callsnext build
. 2. Navigate to your project's settings in the Vercel dashboard, and verify that the "Build Command" is not overridden, or that it callsnext build
. 3. Navigate to your project's settings in the Vercel dashboard, and verify that the "Output Directory" is not overridden. Note thatnext export
does not require you change this setting, even if you customize thenext export
output directory. Learn More: https://err.sh/vercel/vercel/now-next-routes-manifevercelbuildfails.txt
st
Beta Was this translation helpful? Give feedback.
All reactions