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

centralenv

v1.0.6

Published

Central management tool for dotenv (.env)

Downloads

14

Readme

centralenv

Source will be on Github soon... (when finish separating from monorepo)

Motivation

That's just I wanted this function.

Documentation

NOTE:

  • centralenv overwrite output file. You will lost your data if output file already exist.
  • centralenv is not tested. Please use at your own risk.
  • Might not work on Windows. Please let me know if it works or not, since I don't have one.

Install

You can use centralenv for any language if you have nodejs installed on your computer.
Not only for javascript project.

npm i centralenv -D
yarn add -D centralenv

Usage:

Options:

| options | Column B | | ------------------- | ---------------------------------------------- | | -p, --projectName | .env.<projectName>.<stage> | | -h, --help | Show help | | --sourceFile | [default: ".env"] | | --sourceDir | [default: "$HOME"] | | -k, --keySourceFile | [default: ".env.example"] | | -s, --stages | [default: ["development","production","test"]] |

Simple

  • centralenv -s =>

    • .env
  • Source file ${sourceDir}/${sourceFile} => default: $HOME/.env

NAME=UNCHI
EMOJI=💩
CONDITION=VERY_GOOD
PRICE=1010000$
  • <projectRoot>/.env.sample
NAME=N
EMOJI=
CONDITION=?
PRICE=100
NOT_EXISTING_KEY=SomeValue
  • => <projectRoot>/.env
NAME=UNCHI
EMOJI=💩
CONDITION=VERY_GOOD
PRICE=1010000$
NOT_EXISTING_KEY=

Multiple Stages: centralenv

  • centralenv =>
    • output
      • .env.development
      • .env.production
      • .env.test
  • centralenv -s dev -s prod -s someother =>
    • output
      • .env.dev
      • .env.prod
      • .env.someother

.gitignore

.env**
!.env.example

Todo

  • [x] basic functions
  • [x] support stages ['development', 'production', 'test']
  • [x] command line args
  • [ ] log output, by relative path, from project root.
  • [x] generate publish script, to avoid unnecessary devDependencies to be installed.
  • [ ] prefix ( eg: "API_SERVER_" )
  • [ ] encryption / decryption
  • [ ] connect git repo ( using as source with encryption, like fastlane )

CHANGE LOG

1.0.4

BREAKING CHANGE

  • defaultSourceDir was changed from $HOME => $HOME/.env for convenience.
  • Support environment variables with prefix "CENTRALENV".

if you are already using < 1.0.3, you can use same way by doing follows.

echo 'export CENTRALENV_SOURCE_DIR=~/.env ' >> ~/.bash_profile