Felix Haus

Just as bad as you • Software Eng ▲ @vercel

[Felix Haus @ofhouse]

@MelkeyDev The only Datadog graph that matters:

[Felix Haus @ofhouse]

@bengold

[Felix Haus @ofhouse]

@AZ4kii @WorksOnMyLocal @SunilSandhu @vercel @vercel_status Fix is out
https://t.co/gA6fziywhl

[Felix Haus @ofhouse]

@AZ4kii @engineersmantra @SunilSandhu @vercel @vercel_status We rolled out a fix and from our monitoring we're confident that it resolved the issue.

Sorry for the inconveniences ✌️

[Felix Haus @ofhouse]

@AZ4kii @engineersmantra @SunilSandhu @vercel @vercel_status We rolled out a fix and from our monitoring we're confident that it resolved the issue.

Sorry for the inconveniences ✌️

[Felix Haus @ofhouse]

@WorksOnMyLocal @SunilSandhu @vercel @vercel_status Hey, please see this answer for a potential workaround.
Which version of yarn are you using?

https://t.co/fIVtqiW8aI

[Felix Haus @ofhouse]

@SunilSandhu @vercel @vercel_status Hey, yes we're investigating a potential regression after a minor update of the global yarn CLI.

Assuming you're on Yarn 2+?

As a workaround you can try using `$(pwd)` instead of `$PWD` which should still work.

[Felix Haus @ofhouse]

@ramos_pincel @vercel_support The setting inside the package.json takes precedence over what is set in the project settings to allow customers to gradually upgrade monorepos one package at at time.

So >=14 resolves to the latest available runtime (20.x):
https://t.co/Uk1WxGfZ7h

[Felix Haus @ofhouse]

@jarredsumner @DevEngku @vercel Notably the 4s build time include:
- Downloading & installing Bun on the CI
- Installing dependencies
- without any build cache 🤯

[Felix Haus @ofhouse]

@0xPooka @benawad @ThisIsJustUs @Cringe_Idiot @milliHQ So impressive how many people still use @milliHQ✌️🤯

[Felix Haus @ofhouse]

@devuxer @rauchg Have you seen? 👀

[Lee Robinson @leerob]

Vercel Cron Jobs. Next week.

[Felix Haus @ofhouse]

@james_william_r @rauchg Hi, can you provide me the id (from the url) of the deployment where this happened?

[Felix Haus @ofhouse]

@matthewctraul @vercel Hey, we had a busy start into the week, so our investigation is still ongoing.
I was able to reproduce this behaviour with our official Jekyll example and now looking for solutions.
We need to dig a bit deeper for this, but just want to let you know we are on it!

[Felix Haus @ofhouse]

@_peterferguson @vercel @leeerob Ah yeah sorry I misread the update notice as the actual version 🤦🏼‍♂️

[Felix Haus @ofhouse]

@_peterferguson @vercel @leeerob Ah sorry, from the screenshot I see that it is using cli version `28.12.4` and not `28.11.1`
So my question here was to use exactly the this (`28.11.1`) version of the cli:

npx [email protected] build -d

[Felix Haus @ofhouse]

@_peterferguson @vercel @leeerob Hmm, does it also run with the cli version that our CI is currently using (28.11.1)?

npx [email protected] build -d

[Felix Haus @ofhouse]

@_peterferguson @vercel @leeerob Checked back, but could not really see more here as we have no access to the source code.
So the question might sound a bit silly but can you confirm that the following files exist when visiting the repository on https://t.co/aR8fYZd1Py:
- /package.json
- /apps/web/package.json

[Felix Haus @ofhouse]

@isaac_tarib @nextjs @vercel Hey, I would like to take a look what happened here 👋

Can you share your username & the project name with me (DMs open if you do not want to post it publicly)? 🙂

[Felix Haus @ofhouse]

@alcaponeyou Hey, thank you! Especially for all the support you gave to the project! 🙏🏼
I currently see no possibility to work on this further since my priorities now have shifted. So it'll likely be converted into a read only archive soon.

[Felix Haus @ofhouse]

Dropping a new video on the atomic deployments feature that is coming to #Nextjs for AWS 🎉
Full tutorial included, so if you have some time left over the weekend, feel free to try it out!
https://t.co/HsY8SQIfcn