Build errors next js 14 server actions vercel

I created a fresh t3 repo with tailwind, next auth, drizzle and app router. Bumped up next.js and react versions to latest as stated here https://nextjs.org/docs/pages/building-your-application/upgrading/version-14. Build work fine locally, fails on vercel. Tried setting serverActions key in next config to something - the same build output on vercel. Attaching package.json, next config, local build output, error screenshot and serverActions key shape.
No description
No description
No description
No description
No description
24 Replies
Josh
Josh13mo ago
ah, instead of using next 'latest' expliciatly use the latest version
gsemyong
gsemyong13mo ago
Oh, I tried that too Forgot to mention
Josh
Josh13mo ago
regardless if that didnt work, keep it explicitly set, not 'latest'
gsemyong
gsemyong13mo ago
I know dude, thank you for advice
Josh
Josh13mo ago
can you link the repo?
gsemyong
gsemyong13mo ago
Oh, and I am using bun as package manager It is private repo For a client
Josh
Josh13mo ago
try switching to pnpm and see if its a bun issue
gsemyong
gsemyong13mo ago
There is basically nothing there except one server action and some ui stuff
Josh
Josh13mo ago
its looking like next isnt actually getting upgraded
gsemyong
gsemyong13mo ago
Yeah, maybe because of bun lock file
Josh
Josh13mo ago
try killing the lock file, explicitly setting next ver, re-installing, then pushing to vercel
gsemyong
gsemyong13mo ago
Ok, switching to pnpm worked, so I will try to create a new lockfile with bun It can probably be marked as resolved Thanks
Josh
Josh13mo ago
what im guessing happened is because you had it as 'latest', the dep got aggressivly locked in the bun lockfile, and didnt get updated when you pushed to vecel yessir
gsemyong
gsemyong13mo ago
But first thing I set it to 14.0.0 before latest And it didn't work at vercel IDK
Josh
Josh13mo ago
did you do a full reinstall / blow out the bun lockfile
gsemyong
gsemyong13mo ago
I didn't, but before bumping up it was 13.5.8 or something Default t3 version
Josh
Josh13mo ago
thats probably why iirc, installs will always use the lockfile versions, NOT the package.json versions so if you update the package.json but not the lock file, youll have a version mismatch between the two and the builder will favor the lockfile so somehow, it worked on your machine because you installed v14 to your node_modules, but it didnt get into the lock file
gsemyong
gsemyong13mo ago
Yeah, that makes sense Anyways it's bun's issue
Josh
Josh13mo ago
regardless, i hope you now you understand my point on asking questions. here the context was bun, the relevant files, the process you had done to try and fix it already (starting with v14, then trying latest, etc) glad we were able to get the issue resolved tho
gsemyong
gsemyong13mo ago
I understand ofc. The thing I don't agree with is that it didn't require posting new question actually
Josh
Josh13mo ago
oh no you didnt have to hahahah
gsemyong
gsemyong13mo ago
LOL
Josh
Josh13mo ago
you could have appended all this to the OG question i was suprised when you opened a full new one lmao
gsemyong
gsemyong13mo ago
Haaha
Want results from more Discord servers?
Add your server