HomeSandboxShowcaseAppDocBlog
    • EnglishEnglish
      EN
    • русскийRussian
      RU
    • 日本語Japanese
      JA
    • françaisFrench
      FR
    • 한국어Korean
      KO
    • 中文Chinese
      ZH
    • españolSpanish
      ES
    • DeutschGerman
      DE
    • العربيةArabic
      AR
    • italianoItalian
      IT
    • British EnglishBritish English
      EN-GB
    • portuguêsPortuguese
      PT
    • हिन्दीHindi
      HI
    • TürkçeTurkish
      TR
    • polskiPolish
      PL
    • IndonesiaIndonesian
      ID
    • Tiếng ViệtVietnamese
      VI
    • українськаUkrainian
      UK
    /
    Filter docs by framework
    Alt+←
    Why Intlayer ?
    Get Started
    Concept
    • How Intlayer Works
    • Configuration
    • TestFillBuildWatchExtractLoginPushPullConfigurationListVersionEditorLiveDebugDoc ReviewDoc TranslateSDK
    • Visual Editor
    • CMS
    • CI/CD Integration
    • TranslationPluralEnumerationConditionGenderInsertionFileNestingMarkdownHTMLFunction Fetching
    • Per Locale File
    • Compiler
    • Auto Fill
    • Testing
    • Bundle Optimization
    Environment
    • Next.js 14 and App Router
      Next.js 15
      Next.js no locale path
      Next.js and Page Router
      Compiler
    • Tanstack Start Solid
    • Astro and React
      Astro and Svelte
      Astro and Vue
      Astro and Solid
      Astro and Preact
      Astro and Lit
      Astro and Vanilla JS
    • React Router v7
      React Router v7 (fs-routes)
      Compiler
    • Nuxt and Vue
    • Vite and Solid
    • SvelteKit
    • Vite and Preact
    • Vite and Vanilla JS
    • Vite and Lit
    • Angular 19 (Webpack)
      Analog
    • React CRA
    • React Native and Expo
    • Express.js
      NestJS
      Fastify
      Hono
      Adonis
    • Lynx and React
    Plugins
    • JSON
    • gettext (.po)
    VS Code Extension
    Agent
    • MCP Server
    • Agent skills
    Releases
    • v8
    • v7
    • v6
    Benchmark
    • Next.js
    • TanStack
    • Vue
    • Solid
    • Svelte
    Blog
    Ask a question
    1. Documentation
    2. Concept
    3. CLI
    4. Ci
    Creation:2026-01-06Last update:2026-01-06
    Reference this doc to your favorite AI assistant
    ChatGPT
    Claude
    DeepSeek
    Google AI mode
    Gemini
    Perplexity
    Mistral
    Grok

    Ask your question and get a summary of the document by referencing this page and the AI provider of your choice

    Version History

    1. "Add CI command"
      v7.5.111/6/2026
    Edit this doc

    If you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.

    GitHub link to the documentation
    Copy

    Copy doc Markdown to clipboard

    CI Command

    bash
    Copy code

    Copy the code to the clipboard

    npx intlayer ci <command...>

    The CI command is designed for automation and CI/CD pipelines. It automatically injects credentials from the INTLAYER_PROJECT_CREDENTIALS environment variable and can run Intlayer commands across multiple projects in a monorepo.

    How it works

    The CI command operates in two modes:

    1. Single Project Mode: If the current working directory matches one of the project paths in INTLAYER_PROJECT_CREDENTIALS, it runs the command for that specific project only.

    2. Iteration Mode: If no specific project context is detected, it iterates over all configured projects and runs the command for each one.

    Environment Variable

    The command requires the INTLAYER_PROJECT_CREDENTIALS environment variable to be set. This variable should contain a JSON object mapping project paths to their credentials:

    json
    Copy code

    Copy the code to the clipboard

    {  "packages/app": {    "clientId": "your-client-id-1",    "clientSecret": "your-client-secret-1"  },  "packages/admin": {    "clientId": "your-client-id-2",    "clientSecret": "your-client-secret-2"  }}

    Package Manager Detection

    The CI command automatically detects which package manager is being used (npm, yarn, pnpm, or bun) based on the npm_config_user_agent environment variable and uses the appropriate command to execute Intlayer.

    Arguments

    • <command...>: The Intlayer command to execute (e.g., fill, push, build). You can pass any Intlayer command and its arguments.

      Example: npx intlayer ci fill --verbose

      Example: npx intlayer ci push

      Example: npx intlayer ci build

    Examples

    Run a command in single project mode

    If you're in a project directory that matches one of the paths in INTLAYER_PROJECT_CREDENTIALS:

    bash
    Copy code

    Copy the code to the clipboard

    cd packages/appnpx intlayer ci fill

    This will run the fill command with credentials automatically injected for the packages/app project.

    Run a command across all projects

    If you're in a directory that doesn't match any project path, the command will iterate over all configured projects:

    bash
    Copy code

    Copy the code to the clipboard

    cd /path/to/monoreponpx intlayer ci push

    This will run the push command for each project configured in INTLAYER_PROJECT_CREDENTIALS.

    Pass additional flags

    You can pass any flags to the underlying Intlayer command:

    bash
    Copy code

    Copy the code to the clipboard

    npx intlayer ci fill --verbose --mode complete

    Use in CI/CD pipelines

    In your CI/CD configuration (e.g., GitHub Actions, GitLab CI), set the INTLAYER_PROJECT_CREDENTIALS as a secret:

    yaml
    Copy code

    Copy the code to the clipboard

    # GitHub Actions exampleenv:  INTLAYER_PROJECT_CREDENTIALS: ${{ secrets.INTLAYER_PROJECT_CREDENTIALS }}steps:  - name: Fill dictionaries    run: npx intlayer ci fill

    Error Handling

    • If INTLAYER_PROJECT_CREDENTIALS is not set, the command will exit with an error.
    • If INTLAYER_PROJECT_CREDENTIALS is not valid JSON, the command will exit with an error.
    • If a project path doesn't exist, it will be skipped with a warning.
    • If any project fails, the command will exit with a non-zero status code.

    Use Cases

    • Monorepo automation: Run Intlayer commands across multiple projects in a monorepo
    • CI/CD pipelines: Automate dictionary management in continuous integration workflows
    • Bulk operations: Perform the same operation on multiple Intlayer projects at once
    • Secret management: Securely manage credentials for multiple projects using environment variables

    Security Best Practices

    • Store INTLAYER_PROJECT_CREDENTIALS as encrypted secrets in your CI/CD platform
    • Never commit credentials to version control
    • Use environment-specific credentials for different deployment environments
    • Rotate credentials regularly
    Why Intlayer ?
    Alt+→

    In this page

      Discussions are anonymous and regularly reviewed to address common issues. Feel free to share feature ideas, feedback on the documentation, or anything related to Intlayer, we use this input to shape our roadmap and improve the product.

      npx intlayer ci <command...>
      {  "packages/app": {    "clientId": "your-client-id-1",    "clientSecret": "your-client-secret-1"  },  "packages/admin": {    "clientId": "your-client-id-2",    "clientSecret": "your-client-secret-2"  }}
      cd packages/appnpx intlayer ci fill
      cd /path/to/monoreponpx intlayer ci push
      npx intlayer ci fill --verbose --mode complete
      # GitHub Actions exampleenv:  INTLAYER_PROJECT_CREDENTIALS: ${{ secrets.INTLAYER_PROJECT_CREDENTIALS }}steps:  - name: Fill dictionaries    run: npx intlayer ci fill