Felix Haus
689 posts
Felix Haus
@ofhouse
Just as bad as you • Software Eng ▲ @vercel
SH, Germany Katılım Ekim 2010
370 Takip Edilen127 Takipçiler
@ofhouse @WorksOnMyLocal @SunilSandhu @vercel @vercel_status my yarn version is 3.6.1 and I'm having the same error
English
Hey @vercel @vercel_status, we are experiencing an error while trying to deploy our site:
16:43:00.300 Detected Next.js version: 14.0.3
16:43:00.620 Running "yarn run build"
16:43:01.317 Unbound variable "PWD"
16:43:01.342 Error: Command "yarn run build" exited with 1
English
@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 ✌️
English
@WorksOnMyLocal @SunilSandhu @vercel @vercel_status Hey, please see this answer for a potential workaround.
Which version of yarn are you using?
twitter.com/ofhouse/status…
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.
English
English
@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):
#version-overrides-in-package.json" target="_blank" rel="nofollow noopener">vercel.com/docs/functions…
English
@vercel_support Hi, thx for the tip. I made it work for v20 also, but
the setting was:
"engines": {
"node": ">=14"
}
So it only states that the engine should be greater or equal to v14. I would assume that the setting in vercel should indicate the maximum version of node, no?
English
Hey @vercel ! Why are you updating Node runtime versions on projects and not respect what is in the settings?
Today noticed that the runtime was on 20.x, but settings are 18.x
Caused a production error because of that..
#buildinpublic
English
@jarredsumner @DevEngku @vercel Notably the 4s build time include:
- Downloading & installing Bun on the CI
- Installing dependencies
- without any build cache 🤯
English
bun install support is the most upvoted idea of all time in the @vercel github org discussions page
English
@0xPooka @benawad @ThisIsJustUs @Cringe_Idiot @milliHQ So impressive how many people still use @milliHQ✌️🤯
English
If I was starting a new project at work and the nature of the website was something like google forms and classroom, with lots of dynamic forms, tables, charts, etc.
I would use next.js with client-side rendering most of the time and keep my options open for any ssr use-case.
English
What are your top requests for Vercel features & bug fixes?
English
@james_william_r @rauchg Hi, can you provide me the id (from the url) of the deployment where this happened?
English
@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!
English
I have an old Jekyll repo, and em-websocket takes a long long time to install when deploying to @vercel I wonder why that is? This didn’t happen when I used to deploy to gh-pages.
English
@_peterferguson @vercel @leeerob Ah yeah sorry I misread the update notice as the actual version 🤦🏼♂️
English
@_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 vercel@28.11.1 build -d
English
English
@_peterferguson @vercel @leeerob Hmm, does it also run with the cli version that our CI is currently using (28.11.1)?
npx vercel@28.11.1 build -d
English
@_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 github.com:
- /package.json
- /apps/web/package.json
English
@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)? 🙂
English
@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.
English
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!
youtu.be/NY3zKnIcLd4
YouTube
English
The Human Interface Guidelines now has searchable ✨CHANGELOGS✨ developer.apple.com/design/whats-n…
English