Not able to run the project, says I am missing clerk and basehub env variables but they are there

[okanji]

Describe the bug
A clear and concise description of what the bug is.

next-forge version
latest

To Reproduce
Steps to reproduce the behavior:
Follow the installation guide and set up .env variables.
try run the project

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: MacOS
• Browser: Chrome

[julianbenegas]

hey @okanji, do you have the env variables in an .env.local, or what's the file name you placed them on?

[okanji]

Yes, .env.local in all the places described in the docs On Jan 14, 2025, at 5:13 PM, Julian Benegas ***@***.***> wrote: hey @okanji, do you have the env variables in an .env.local, or what's the file name you placed them on? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[haydenbleasel]

@okanji Can you specifically tell us the paths of your .env.local and .env files?

[okanji]

Hi @haydenbleasel , yes here it is:

apps/app/.env.local

apps/web/.env.local

apps/api/.env.local

packages/databse/.env

packages/cms/.env.local

I get the following errors:

Note that these are the .env.local variables for clerk (I have replaced the publishing key just for this screenshot but the rest are as in the example):

[barsketis]

I am able to replicate this bug sometimes, but im not sure what is causing it to go away. I think turbo might be storing a cache if you tried building without the env's set across the whole process, for example the cms env or the web env. Turbo has some interesting behaviour for env's vercel/turborepo#8424

Here are some steps that might make it go away

clean the cms and web, then install from the parent repo

# cd into apps/web
pnpm clean

# cd into packages/cms
pnpm clean

# cd back to parent root folder
pnpm clean
pnpm i

# cd back to apps/web
pnpm dev

if that doesnt work try it in reverse

# from the main repo clean the parent install but dont install right away, instead install the subpackages first
pnpm clean

# cd into packages/cms
pnpm clean
pnpm i

# cd into apps/web
pnpm clean
pnpm i

# then see if the web project builds
pnpm dev