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

config-env-file

v4.0.1

Published

A command line to generate a .env file based on a Config

Downloads

12

Readme

CONFIG ENV FILE

A command line to generate a .env file based on a Config

Why?

If you have a config in a json format and you don't want to expose your config to the public, you can pass it to a .env file but make a .env file by hand with the json file may take a while. This command will generate a .env file for you.

Install

# npm
npm install -g config-env-file
# npx
npx config-env-file [config-file] [options]
# yarn
yarn global add config-env-file

Usage

cef ./config.json
# config.json: { "api": 1, "key": 2 }
# output:
#   const config = {
#     api: process.env.API,
#     key: process.env.KEY
#   }
# .env.local:
#   API="1"
#   KEY="2"

Example with a firebase project

When you use firebase in your app, you might not want to expose the firebase config. Pass the config to an .env file may take a while doing it by hand. This is a simple example to generate a .env file from a firebase config.

touch firebase.config.json
# copy the firebase config to firebase.config.json
# firebase.config.json:
# { "apiKey": "example", "authDomain": "example.firebaseapp.com", ... }

cef firebase.config.json
# .env.local:
# API_KEY="example"
# AUTH_DOMAIN="example.firebaseapp.com"
# ...

# output:
# const config = {
#   apiKey: process.env.API_KEY,
#   authDomain: process.env.AUTH_DOMAIN
#   ...
# }

Options

Prefix

add prefix to variables name. default undefined

cef ./config.json --prefix public
# config.json: { "apiUrl": "https://..." }
# output:
#   const config = {
#     apiUrl: process.env.PUBLIC_API_URL,
#   }
# .env.local:
#   PUBLIC_API_URL="https://..."

Include Objects Values

whether to include object values or not. default false.

# config: { "api": 6, "client": { "id": 1, "secret": 6 } }

cef ./config.json
# .env.local:
#   API="6"

cef ./config.json --include-objects
# .env.local:
#   API="6"
#   CLIENT="{"id":1,"secret":6}"

Env

how to access variables. choices "process", "import". default "process".

cef ./config.json --env import
# output:
#   const config = {
#     api: import.meta.env.API,
#     key: import.meta.env.KEY
#   }

Other options

  • destination: destination path to env file. default ".".
  • extension: extension to env file name. default "local".
  • single-quotes: use single quotes in env values. default false.
  • no-quotes: don't add quotes to env values. default false.
  • silent: skip console logs. default false.

Run cef --help for more information.