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

levgen

v0.0.1

Published

Package used to generate .env from package.json configuration to enable local development when env is git ignored

Downloads

4

Readme

Local Environment Variable Generator

Levgen is a small npm package that generates\updates an .env.local (default) file from configuration set in a projects package.json file. The purpose is to store the configuration keys in the package.json but not to have a .env file associated into source control.

Local Config

To use add a env section in your package.json file

...
"env": [
{
  "__comment": "This is a header",
  "values": ["ENV_VALUE_ONE", "ENV_VALUE_TWO"]
}],
...

The env section must be an array and can contain a mixture of strings and objects. If an object exists it must atleast contain a key named values declared as an array. The __comment key is optional but it will write that first before the values grouping them together.

Running

As of npm 5.2.0 npx (nodes package runner) is available. Thus, there is no need to directly Install Levgen and instead can be ran in the terminal using

npx levgen

Options

-v, --version      output the version number
-c, --clobber      should values in env file be removed if they no longer exist in config (default: false)
-n, --name [name]  override the output file name that env variables are written to (default: ".env.local")
-h, --help         output usage information

Usage

npx levgen --clobber

Note

This is a basic first itteration. Please report any bugs found and or make a pull request and I will get them resolved as soon as possible.

Todo

As of 09/07/2019

  • Optimizations / Refactoring
  • Better Error Handling