npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

nvenv-cli

v0.1.3

Published

nv CLI - Environment variable management with Vercel-like DX

Readme

nv CLI

Environment variable management with Vercel-like developer experience.

Installation

npm install -g nvenv-cli
# or
bun add -g nvenv-cli
# or
pnpm add -g nvenv-cli

Quick Start

# Authenticate with your nv account
nv login

# List your workspaces
nv list

# Link to a workspace
nv link --workspace <workspace-id>

# Pull environment variables
nv pull --env production

# Pull to a custom file
nv pull --env development --output .env.local

Commands

nv login

Authenticate with nv via browser. This will:

  1. Generate a unique verification code
  2. Open your browser for confirmation
  3. Save your authentication token locally
nv login

nv logout

Log out from your nv account and remove stored credentials.

nv logout

nv list (alias: ls)

List all your workspaces.

nv list
# or
nv ls

nv link

Link the current directory to a workspace. Once linked, you can use nv pull without specifying the workspace ID.

# Link to a workspace
nv link --workspace <workspace-id>

# Show current linked workspace
nv link

Options:

  • -w, --workspace <id> - Workspace ID to link

nv pull

Pull environment variables from a workspace and save them to a local file.

# Pull development variables (default)
nv pull

# Pull production variables
nv pull --env production

# Pull from a specific workspace
nv pull --workspace <workspace-id> --env production

# Save to a custom file
nv pull --env production --output .env.production.local

Options:

  • -e, --env <env> - Environment (production, preview, development). Default: development
  • -w, --workspace <id> - Workspace ID (optional if linked)
  • -o, --output <file> - Output file path. Default: .env.<env>.local

Configuration

The CLI stores configuration in your system's config directory:

  • macOS: ~/Library/Preferences/nv-cli-nodejs
  • Linux: ~/.config/nv-cli
  • Windows: %APPDATA%\nv-cli\Config

Configuration includes:

  • apiUrl - API endpoint (default: https://nvenv.dev)
  • accessToken - Authentication token
  • currentWorkspace - Linked workspace ID

Environment Variables

You can customize the API URL using an environment variable:

export NV_API_URL=https://your-nv-instance.com
nv login

Examples

Typical Workflow

# 1. Login
nv login

# 2. List workspaces to find the one you need
nv list

# 3. Link to your project workspace
nv link --workspace abc123

# 4. Pull production variables
nv pull --env production

# 5. Pull development variables for local development
nv pull --env development --output .env.local

CI/CD Integration

For CI/CD environments, you can skip the link step by always specifying the workspace:

nv pull --workspace $WORKSPACE_ID --env production --output .env.production

License

MIT