bug: unable to detect my google env key during build

[shashwat-runable]

What's happening?

lingoCompilerPlugin({
      sourceRoot: "src",
      sourceLocale: "en",
      targetLocales: ["es", "de", "fr"],
       models: {
          "*:*": "google:gemini-2.0-flash",
      },
      dev: {
        usePseudotranslator: false,
      },
    }),

This is my config and the compiler is unable to recognize my google api key even though its there in my env as well as exported it from the terminal

Exact Reproduction Steps

1. Use the above config
2. Setup the google api key

Expected

Should have detected the key.

Actual

Unable to recognize my google key.

Screenshots/Videos

[vrcprl]

@shashwat-runable Which compiler version are you using?

[shashwat-runable]

@shashwat-runable Which compiler version are you using?

its 0.3.3

[vrcprl]

Thanks for reporting, @shashwat-runable! The team is looking into it and trying to reproduce it. We’ll reach out if we need more context.

[JGarima2843]

Hi maintainers — I’d like to help fix this. Can you please assign me to #1946?

What I’m seeing / hypothesis

For Gemini/Google, the official env var names commonly used by Google SDKs are GEMINI_API_KEY or GOOGLE_API_KEY (with GOOGLE_API_KEY taking precedence if both are set).

In monorepos using Turborepo, env vars may not be available to tasks depending on envMode / allowlists (e.g., strict mode), unless explicitly passed via globalEnv, globalPassThroughEnv, or task-level env.
This could explain “it’s exported in my terminal” but the compiler process still sees undefined.

If assigned, I can work on a fix

1. Ensure the compiler’s Google provider checks both GOOGLE_API_KEY and GEMINI_API_KEY (and emits a clearer error telling users exactly which vars are accepted).
2. Add a docs note for Turbo users about passing env vars in strict mode.
3. Add a small unit/integration test that fails when env vars aren’t present and verifies the error message.

[vrcprl]

assigning to you @JGarima2843 !