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

enveg

v0.1.1

Published

A simple generator to generate environment variables example file.

Downloads

21

Readme

Enveg (Env Example Generator)

Generate your .env example faster and easier 🚀

Demo



# VERSION 1 OF API KEY
API_KEY_V1 = "KEY_XXXX_XXX_XXX"
# VERSION 2 OF API KEY
API_KEY_V2 = "KEY2_XXXX_XXX_XXX"

# ONE COMMENT 
# DOUBLE COMMENT
# TRIPLE COMMENT
HOW_MANY_COMMENTS = 3

@ignore
IGNORE_ME = "OKAY YOU ARE IGNORED"



# VERSION 1 OF API KEY
API_KEY_V1 = YOUR_API_KEY_V1 


# VERSION 2 OF API KEY
API_KEY_V2 = YOUR_API_KEY_V2 


# ONE COMMENT 
# DOUBLE COMMENT
# TRIPLE COMMENT
HOW_MANY_COMMENTS = YOUR_HOW_MANY_COMMENTS

Command used

enveg -c -l 2

Installation

  npm i -g enveg

Usage

Simple:

  # Open terminal in the desired directory and run:
  enveg
  # it will pick current directory .env and run with default options

Advanced:

  # Open terminal in the desired directory and run:
  enveg [options]
  # e.g
  enveg -c -p "./config/.env" -s DEMO_SLUG -l 2
  
  # to ignore a key add `@ignore` before it

Options (optional)

  • -p OR --path followed by the path of your .env file (relative or absolute path support), default is current terminal directory, it will pick the .env file in it if there's any.
  • -c OR --comments to include comments, by default comments are removed after parsing
  • -e OR --empty to replace values by empty space, by default values are replaced by default_slug (YOUR) + key
  • -s OR --slug followed by the desired slug that you want to add to the value, default is YOUR
  • -l OR --linespace followed by an integer indicating the line-breaks amount between each env variable, default is 1