Same thing happen for our team this morning

Quick update, I believe Vercel change how it does its builds relating to Next. It really doesnt look like Vercel is going to revert the changes either.

I've got a workaround for the issue currently. If you continue to have such build error let me know, I'll help you out

Why don’t you share your fix directly for others to be able to apply it as well rather than having to contact you.

Same here!

Was debuggin it for 30mins until I came here and saw I'm not the first one, I can't get rid of it! Looking for help! ❤️

yea, share it with everyone. As you can see more than one person have this issue

The only workaround I see

{
  "compilerOptions": {
    "noImplicitAny": false
  }
}

which is ofc 2head move and would love to see something better

EDIT: Okay, it doesn't even work

Could you share your workaround?

BTW from what I undestand it's vercel team issue and they should fix this regardless?

Right now it looks pretty normal https://www.vercel-status.com/

yep facing the same issue here

I tried migrating eslint from v8 to v9 but still having the same issue.

anyone with a workaround or is it a vercel problem?
I mean it seems to work fine when I run next build locally

nvm it still doesn't work 😢

because in this instance, best chance of it is to wait it out. Original intent was for those individuals with an production level problem might want to hear what I got

But anyways, for most people with this error's sudden appearance , is due to the fact that Vercel now has a different default method of going through your codes for making sure that your code is safe

(Even though depending on the size of your project, you would most likely encounter another similar error)

For those that are using Next.js for front end deployment and received the same error message as the OG post

I recommend the following work around

1. Locate to your tsconfig.json

2. add '.next' to exclude it.

After pushing change, you should no longer see that error message as it is now excluded from the list of thing vercel checks

@B33fb0n3 @Brown bear

Note, even though you make it pass this particular error, there's a high chance you will encounter 'other' new error message.

If so, post it on the forum and lets have a look together!

@Common House-Martin still get the same error after implementing your workaround

Works for me

ayt so you just tell Vercel to not check Next files

make sure you remove all reference of Next files on your tsconfig

I know by default

you would see ".next/types/*/.ts" under your include

@Giant panda yep it worked 😂
Thanks for the help brother you saved my day lol

I just checked my deployments and have no problem. Even without your solution. So you might want to check your code as well ^^

Oh nice, did vercel address this?

Today marks a very confusing day for us Vercel users hh

I think there is something inside the code, so the error happens. I guess vercel itself never had any problem. It looks more like the code itself causes the problem

I don’t think that’s necessarily the case for these guys as the error clearly indicates “next” packages causing error

But I’m glad you are no longer having this issue! Congrats

I never had the issue

probably they had an issue and already fixed it. if a deployment worked before but its redeployment fails (even with cache disabled), it's always vercel's fault.

nice nice

finally! ❤️

yesss!!

👏

🫡

🫡