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 🙏

© 2026 – Pkg Stats / Ryan Hefner

interactive-env

v1.0.0

Published

Simple command line tool for initialising your environment variables

Readme

interactive-env

Travis npm license

Simple Node.js command line tool for initialising your environment variables

asciicast

Installation

You can install interactive-env globally so you can use it across all of your projects, or as a dependency in package.json so that everyone who works on the project can use it.

Global Install

npm install --global interactive-env

Local Install

npm install --save-dev interactive-env

Usage

Global Install

If you have interactive-env installed globally, you can run it directly from the command line.

$ interactive-env

Local Install

If you have interactive-env installed as a dependency in a project, you can run it from the node_modules/.bin folder.

$ ./node_modules/.bin/interactive-env

However, I recommend that you add it as an npm script in your package.json to make it easier for you and anyone else working on your project.

{
  ...
  "scripts": {
    "env": "interactive-env"
    ...
  },
  ...
}
$ npm run env