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

@liangchun/envconf

v1.1.1

Published

An interactive command line interface for setting up and syncing env files based on a template

Downloads

10

Readme

envconf

An interactive command line interface for setting up and syncing env files based on a template

Usage

# set up or sync env files from `envconf.toml`
# (by default it will look it up on the cwd)
envconf

# help
envconf --help

Configuration

Create a envconf.toml file with the following format:

[files]

[files.example1]
template = "./test/example1/.env.sample"
output = "./test/example1/.env"
allow-empty = ["IGNORED_ENV"]
force-prompt-on-create = ["FORCED_PROMPT_WITH_DEFAULT_VALUE"]

[files.example2]
template = "./test/example2/.env.local.sample"
output = "./test/example2/.env.local"

Fields

  • template: the template file which the env file should be generated from
  • output: the output env file which will be generated
  • allow-empty
    • Ignores the envs on creation and copies it as-is with the value set to an empty string
    • If the output file already exists and does not contain the variables specified in allow-empty, it will prompt to fill in as blank
  • force-prompt-on-create: forces a prompt on create for the given env variables even though they have default values

Behaviours

On creation of the env file

  • Prompts for all env variables which do not have default value in the template
  • Env variables which are inside allow-empty will be automatically copied with the value set to empty

On sync (existing env file)

  • Prompts for all missing env variables from the template file which are not in the output file
  • If there is a default value for an env variable which is not set, pressing ENTER when prompted will fill in the default value
  • If an env variable is inside allow-empty and is not set, it will prompt to add it as empty to the output file