Issue with process.env variables causing configuration error in Sanity client setup.

Hi All, up until this morning, my Sanity client config was working properly reading from .env and now it isn't. I have this as the client setup:
Now it's throwing `Uncaught Error: Configuration must contain `projectId``

If I hardcode the dataset name and project ID in the options object, it works fine.

Anyone else running into this?

Hardcoded, it has all the vars fine. From process.env, it doesn't even get that far. It errors on initConfig

I tried this: https://stackoverflow.com/questions/70368760/react-uncaught-referenceerror-process-is-not-defined
And this:
https://stackoverflow.com/questions/71451219/uncaught-error-configuration-must-contain-projectid-when-using-environment-v
With no success

I also tried pulling out those vars into consts using destructuring on process.env above

options

and got an error saying process is undefined. This is running dev, not build + production

Got it. Since you said it had been working previously, did you change anything about your env file?

.env and the sanity client init file were unchanged. The biggest change related was moving the usage from getStaticProps (next.js) to useEffect

The fact that process was undefined with the destructuring approach leads me to believe it's probably not a sanity issue, but I thought maybe someone else here might have had the same problem.

It does seem like it isn't a Sanity issue, but there have been a ton of questions around how to use env vars lately. Definitely still helpful to debug here! Are you able to share your repo so I can take a look? You can send me a zip of it over DM if you don't want it to be public.
Also sidenote, it's not necessary to obscure your dataset name and project id. Those will be publicly visible when you perform a query. They're not considered secret in the same way an API token it.

Sorry, not allowed to share the repo or codebase. I appreciate the offer to help though! I'll try to figure it out with my teammates.

I figured out the problem and thought I'd let you know in case someone else runs into it. It was an issue with env vars in next.js as explained here: https://nextjs.org/docs/api-reference/next.config.js/environment-variables

Thanks for the update Jim! Really appreciate it!