Trek Glowacki
Trek Glowacki
@cosn do you recall the last know good (for your use) cli version? I've gone back a month and can't get see any differences in the call we make to...
@cosn that is true, but not everyone can update to latest cli and not everyone uses the cli. Were you able to reproduce this with a last known-good cli version?
@cosn we're trying to track down an API change that would have caused this and can't identify an issue. This may be a bit more of a feature request and...
Hi @NicholasHoff Thanks for reaching out! We use this Issue tracker for bugs in the Vercel CLI and related open source libraries. For general platform help and feedback please open...
This was related to an ongoing issue that should be resolved now. Please let us know if it persists.
@azf20 we're looking into it. Thank you for the great reproduction!
Hi @akinwol, We're getting close to releasing a feature that may help here. https://x.com/leeerob/status/1669830877759635457
`VERCEL_ENV=development` and `VERCEL=1` should be restored in the next release.
@rajdtta this should Just Work ™ https://github.com/vercel/vercel/blob/defe8eacc4e56c2b66ff3fff8326e94f0823020f/packages/next/src/index.ts#L241-L244
Closing for now. We bumped majors for the break, restored some `VERCEL_` in the dev server a bit ago. For more info on this decision https://community.vercel.com/t/vercel-system-environment-variables-not-loaded-in-development/6649/8