envpicker

A simple CLI tool for managing multiple environment files in your Node.js projects.

Overview

envpicker helps developers easily manage and switch between different environment files (.env) in their local development environment. It provides simple commands to initialize, list, activate, and delete environment configurations.

Installation

Install globally using npm:

npm install -g envpicker

Or use directly with npx:

npx envpicker [command]

Usage

Available Commands

envpicker [command]

Commands:
  list | ls               List all available environments
  activate | use [env]    Switch to specified environment
  save [env]              Save current .env to /env directory
  deactivate | stop       Remove active environment
  init                    Initialize default environment files
  delete [env]            Delete specific environment file

Basic Operations

1. Initialize default environment files:

envpicker init

This will create:

• env/.env.development
• env/.env.staging
• env/.env.production

2. List available environments:

envpicker list

3. Activate an environment:

envpicker activate development

4. Deactivate current environment:

envpicker deactivate

5. Delete an environment:

envpicker delete development

6. Save an environment:

envpicker save development

File Structure

The tool expects your project to have the following structure:

your-project/
├── env/
│   ├── .env.development
│   ├── .env.staging
│   └── .env.production
├── .env (created when environment is activated)
└── package.json

Requirements

• Node.js
• Bash/Shell environment

Limitations

• CLI-only tool (no GUI interface)
• Designed for local development use

Bug Reports and Feature Requests

Please submit any bugs or feature requests to our issues page.

License

ISC License

Security

Note: This tool is intended for local development use only. Be careful with your environment files and never commit them to version control.