Follow up on NODE_ENV no longer set in runtime

NODE_ENV no longer set in runtime

Follow up on NODE_ENV no longer set in runtime

I wanted to follow up on the issue I opened last week: https://community.vercel.com/t/node-env-no-longer-set-in-runtime/1131 First, thank you for addressing it promptly. It does...

NODE_ENV no longer set in runtime

We're not changing the NODE_ENV for the runtime environment, we are just using zod to make referencing the env variable type safe. It's been working fine for about 9 months and...

NODE_ENV no longer set in runtime

That looks like the build environment, not the production runtime environment. I'll see about doing a minimal example if I get a free moment. I'd suspect anyone using zod and is...

NODE_ENV no longer set in runtime

This is exactly the error we were seeing. Our workaround was to remove `NODE_ENV` from the zod validation and switch to `process.env.VERCEL_ENV` anywhere we were previously relying...

NODE_ENV no longer set in runtime

Would you be able to look it up from the log request id? I'm hesitant to share too much in a public forum.

NODE_ENV no longer set in runtime

Thanks for looking into it. I'm not sure which app you looked at, but our production app is using Remix. We haven't updated the Remix framework for a few months, so it doesn't make...

NODE_ENV no longer set in runtime

We were previously relying on NODE_ENV being set in production and it doesn't appear to be set any more. Additionally if we manually set NODE_ENV to 'production', dev dependencies...