You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
Hmm, I'm not able to reproduce that build failure, but I believe it's due to us putting a client side file into /api which Vercel tries to deploy as a serverless function.
I came across some surprising behavior by Vercel when I deployed using that button which was that it did not detect the project as a Next.js app. This was easy to fix by setting the Framework Preset to Next.js in Settings -> General. I will look into why Vercel is not detecting this as a Next.js app.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When deploying with the vercel button, after entering environment variables, the build fails with:
Error: EEXIST: file already exists, symlink 'spaces.func' -> '/vercel/output/functions/api/token.func'
The text was updated successfully, but these errors were encountered: