Skip to content

Lingo.dev Compiler unexpectedly requires GROQ_API_KEY even when configured to use only Google Gemini model #1737

@iurvish

Description

@iurvish

What's happening?

🐛 Bug Report

Describe the bug
When running the Lingo.dev Compiler in my Vite (monorepo)project with only the Google Gemini model configured, build starts translating successfully, but then fails part-way with:

Exact Reproduction Steps

Even though I only configured Google (Gemini) in my models setting, and I have a valid GOOGLE_API_KEY, the compiler still tries to use Groq and errors if GROQ_API_KEY is not present.


plugins: [
    lingoCompilerPlugin({
      sourceRoot: "src",
      sourceLocale: "en",
      targetLocales: ["es", "de", "fr"],
      models: {
        // "en:es": "google:gemini-2.5-flash", 
        // "en:de": "google:gemini-2.5-flash", 
        // "en:fr": "google:gemini-2.5-flash",
        "*:*": "google:gemini-2.5-flash", 
      },
      dev: {
        usePseudotranslator: true,
      },

Expected

.

Actual

.

Screenshots/Videos

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions