Go Behind the Experience to see how Tecovas brings the West to life with Sanity 🤠 July 18th

Issue with environment variables in a NextJS and Sanity app, seeking help and suggestions.

18 replies
Last updated: Nov 22, 2021
Hello 🙂I have reasons to believe that my Sanity & NextJS app have a problem using environment variables
Nov 20, 2021, 12:12 PM
they yield an
Nov 20, 2021, 12:13 PM
according to the following, it might have something to do with
which is featured on Sanity https://github.com/vercel/next.js/discussions/12754#discussioncomment-13033
Nov 20, 2021, 12:13 PM
my question is: is it ok to remove the package from Studio?
Nov 20, 2021, 12:14 PM
hmm actually, I don’t think that will be possible, am I right?
Nov 20, 2021, 12:22 PM
any other ideas as to how to fix this issue please?
Nov 20, 2021, 12:22 PM
this is the code I’m working on https://github.com/eugelogic/gothenburg
Nov 20, 2021, 12:37 PM
Hi Eugene - perhaps you've already been down this road, but I banged my head on the .env for a while until I found in the docs that for the studio you need to prefix them with
. Is that any help? https://www.sanity.io/docs/studio-environment-variables#f5e9e3158896
Nov 20, 2021, 1:40 PM
Hi Joseph, thanks for getting back to me.I did not know about that, good to know.
Unfortunately my issue lives in the NextJS part of my project and I need to prefix the variables with
This is really puzzling, I’ve spent hours and read lots but whatever I find is related to either NextJS or Sanity, no the two together, I can’t believe I’m the only one facing such issue
Nov 20, 2021, 8:22 PM
or maybe I’m missing something obvious, it might worth mentioning I use Lerna and Yarn Workspaces 🙄
Nov 20, 2021, 8:25 PM
Hi - I don't have particular experience with Next and I don't do any monorepo stuff regularly (having 2+ repos has worked for me, but I do most projects solo). But maybe it's something to do with how your build process is configured with Lerna? Have you tried making a copy of your Next repo and running a build on it locally to see if that build will incorporate your environment variables correctly? That way you could rule out any weird syntax mistake you might be missing on the Next side of things?
Nov 21, 2021, 11:24 AM
Could you share the bit of code where you use the env variables that turned out to be undefined & also where you put them? .env.local?
Nov 21, 2021, 2:22 PM
user U
I did try to run
but it would flag that the env variable is
also tried to hardcode the actual value of the env variable and it did work so it’s something to do with
I guess
Nov 22, 2021, 9:35 AM
user G
the code lives at https://github.com/eugelogic/gothenburg/blob/main/web/lib/config.js and my env variables live in a
file in the root of the repo which of course you can’t see online because I’m not committing it GitHub
Nov 22, 2021, 9:37 AM
Just to be clear, the .env.local is in the
directory and not the root directory, is that correct? Because I think Next wouldn’t see it otherwise
Nov 22, 2021, 9:41 AM
no it’s in the root of the project, not inside the
folderI did read somewhere Next would be able to see it regardless
+ I did move it inside to see if that was the issue, re-started the server but it didn’t help, lemme try again
Nov 22, 2021, 9:44 AM
lol -
user G
it works 😅I have no idea why it didn’t when I tried the other day but it does now
thanks for making trying again
Nov 22, 2021, 9:54 AM
Nice! Glad you got it figured out!
Nov 22, 2021, 9:55 AM
much appreciated 🙏
Nov 22, 2021, 9:56 AM

Sanity– build remarkable experiences at scale

Sanity is a modern headless CMS that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Was this answer helpful?