Environment variables not passing through to turbo command as described in documentation #7056
Replies: 2 comments
-
I don't see anything obviously wrong with your setup. If you don't see the same issue with running |
Beta Was this translation helpful? Give feedback.
0 replies
-
Closing for staleness. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been trying to get
dotenv-cli
working as per the suggested setup on Turborepo's monorepo handbook. I've got the followingpackage.json
:I get a very odd error in my terminal when running
pnpm build
,pnpm dev
, or any of the other commands withdotenv --
:Of course, I could just pass the
--remote-only
flag, but then I get the same warning about the--summarize
flag. Without attaching every flag that Turborepo's CLI offers, how can I fix this?A few interesting notes/things I've already tried:
npm
oryarn
instead returns the same resultdotenv ...
instead ofdotenv -- ...
returns the same resultpnpm dev
and any other the other commands returns the same result aspnpm build
- it's not isolated to thebuild
scriptdotenv-cli
andturbo
1-3 minor versions each returns the same resultnode_modules
folder and runningpnpm install
again returns the same resultturbo run build
works perfectly, but then it doesn't include the environment variables in the builddotenv -- pnpx cowsay hello
works perfectly fine, so I don't think this has to do withdotenv-cli
so much asturbo
not using its default flags correctly when unspecifiedBeta Was this translation helpful? Give feedback.
All reactions