Recently, I started working with Turborepo and encountered a situation where I needed environment variables in the root directory. However, I didn’t want to rely on the environment variables of my linked projects, as they contain values specific to each project.
This seemed like an ideal use case for shared variables. Since these values are already connected to my apps, having the option to link only them in the root directory feels like a natural solution.
The Idea:
Add the ability to link shared variables in the project.
From what you’re describing, it sounds like we support what you’re looking for today:
This way, you won’t need to use a .env file in the root of your repository, following best practices, and can have a stored of shared variables.
1 Like
Thanks for the quick response, but if I understand correctly, it’s not exactly what I am looking for. Let me explain it in more detail. In my Turborepo, I have two apps. Both apps are under the same team and linked as different projects, so when I run vercel pull, I get different environments for each of them. They both use the same database, so I have the same DATABASE_URL in the environment variables set in the shared environment. That all works fine, but since I have a package that uses the DATABASE_URL (the same shared one across both applications), I wish I could somehow link the root of the project to pull only the environment variables shared across both projects.