Streamline Your Workflow: Effortlessly Convert JSON Configuration to .env Files

The Developer's Configuration Dilemma

Every developer has faced this frustrating scenario: you have a perfectly organized JSON configuration file, but your deployment pipeline demands a .env file. Your Docker containers expect environment variables, your CI/CD tools read dotenv format, and your serverless platform only accepts key-value pairs. The result? You spend precious time manually copying each entry, writing another one-off script, or—worse—reformatting data that should take seconds. This repetitive task not only kills productivity but also introduces typos and inconsistencies across environments. Fortunately, there's a smarter way to bridge the gap between JSON and dotenv formats without the headache.

A Lightweight Converter for Instant Results

@sourcepride/json-to-env is a compact Node.js library designed to transform JSON objects into dotenv-style environment variables in a single command. No manual translation, no custom glue code—just a clean, reliable conversion. Whether you're working locally or integrating into a deployment pipeline, this tool strips away the friction and lets you focus on what matters: your application logic.

Where This Tool Shines

Docker and Container Deployments

Microservices thrive on JSON configurations during development, but production containers—whether managed with Docker Compose or Kubernetes—prefer environment variables. The old approach meant manually translating config.json into .env, a process infamous for being error-prone and tedious. With json-to-env, you simply run a single command and the conversion happens in seconds:

npx json-to-env ./config.json ./.env

CI/CD Pipeline Integration

Modern CI/CD platforms like GitHub Actions, GitLab CI, and CircleCI rely heavily on environment variables. However, your secret management system (such as AWS Parameter Store or Azure Key Vault) might deliver configurations in JSON. Instead of writing a custom script to parse and export each variable, you can call the library directly in your build script:

import { jsonToEnv } from "@sourcepride/json-to-env";

const config = await fetchFromVault();
const envVars = jsonToEnv(config);
// Inject envVars into your pipeline's context

Multi-Environment Management

Maintaining separate JSON files for development, staging, and production is a common practice. The headache begins when you need corresponding .env files for tools that don't understand JSON. With json-to-env, you can convert all environments at once with simple shell commands:

json-to-env ./config.dev.json ./.env.dev
json-to-env ./config.staging.json ./.env.staging
json-to-env ./config.prod.json ./.env.production

Bridging Legacy Systems

Your new microservices speak JSON, but the legacy deployment platform—perhaps built in 2015—only understands .env files. Rather than maintaining duplicate configuration sets, use json-to-env as a seamless bridge. You keep a single source of truth in JSON and generate the required dotenv file on the fly during deployment.

Serverless Function Deployment

AWS Lambda, Google Cloud Functions, and Azure Functions all accept environment variables. Instead of manually entering each key-value pair in the cloud console, incorporate json-to-env into your deployment script:

const envConfig = jsonToEnv(serverlessConfig);
// Upload envConfig to your cloud provider's function configuration

Features That Simplify Your Work

Handling Nested Objects

Complex JSON configurations often have nested structures. json-to-env automatically flattens them into dotenv-compatible keys using an underscore separator, so database.credentials.username becomes DATABASE_CREDENTIALS_USERNAME. For example:

jsonToEnv({
  database: {
    host: "localhost",
    port: 5432,
    credentials: {
      username: "admin",
      password: "secret"
    }
  }
});
// Outputs:
// DATABASE_HOST=localhost
// DATABASE_PORT=5432
// DATABASE_CREDENTIALS_USERNAME=admin
// DATABASE_CREDENTIALS_PASSWORD=secret

Working with Arrays

Arrays in your JSON aren't a problem. The library converts them into indexed keys, making even list-based configurations easy to export. For instance, an array of allowed hosts becomes ALLOWED_HOSTS_0, ALLOWED_HOSTS_1, and so on. This consistent mapping ensures no data loss during the conversion.

How to Get Started

Integrating json-to-env into your project is straightforward. Install the package via npm:

npm install @sourcepride/json-to-env

Then use the CLI tool or import the library directly in your Node.js code. The use cases above demonstrate versatile applications, but the core command is always the same: pass your JSON input and—optionally—an output file path. Within seconds you'll have a clean .env file ready for any environment.

Stop wasting time on manual configuration translation. Embrace a tool that does the heavy lifting, keeps your deployments consistent, and frees you up for more valuable development work. With json-to-env, the gap between JSON and dotenv disappears—instantly.