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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@nodefactory/env-prompt

v1.0.8

Published

A dependency-free utility that prompts you for your project's environment variables.

Downloads

6

Readme

env-prompt

A dependency-free utility that prompts you for your project's environment variables.

How does it work?

On npm install, env-prompt reads environment variables from two files in your project:

  • a distributed file (default: .env.dist)
  • a git ignored local file (default: .env)

Env-prompt will diff these two files, prompting you for any values that exist in your distributed file but not in your local file. Your newly input values will be written to your local environment file.

Getting started

  1. Install env-prompt:
$ npm install -D env-prompt
  1. Add a postinstall hook to your package.json file:
{
  "name": "test",
  "main": "index.js",
+ "scripts": {
+   "postinstall": "env-prompt"
+ },
  "devDependencies": {
    "env-prompt": "^1.0.0"
  }
}
  1. Create a .env.dist file in the same directory as your package.json file:
DB_USER=root
DB_PASS=root123
DB_HOST=127.0.0.1
DB_PORT=3306
DB_NAME=sakila

Env-prompt is now setup, and will be triggered when you run npm install.

Options

-d, --distFile <path>
       Change the distributed environment file env-prompt reads from. (default: .env.dist)

-l, --localFile <path>
       Change the local environment file env-prompt reads from and writes to. (default: .env)

Product backlog

Is your use case not covered? Feel free to open an issue.