Sanity CLI does not set NODE_ENV

[selrond]

When using sanity CLI commands, NODE_ENV does not appear to be set.

My usecase was to customize the basePath in sanity.cli.ts based on the NODE_ENV.

To verify:

1. clone the official Next.js starter: https://github.com/sanity-io/sanity-template-nextjs-clean
2. add console.log(process.env) to sanity.cli.ts
3. try to run npx sanity dev for instance, observe NODE_ENV not being among the variables

[osnoser1]

I have the same problem. I'm reading in the docs that the NODE_ENV variable is set when sanity build or deploy is run, but for some reason, this isn't the case when I print it in the sanity.cli.ts file.

Doc ref: https://www.sanity.io/docs/environment-variables#7f90f065848c

[thobas-dnvgl]

Almost the same here, I tried to read NODE_ENV from sanity.config.ts without success.

[rexxars]

This issue has been moved from sanity-io/sanity as part of a CLI issue migration. We will investigate whether it is still relevant.