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

uni-envs

v1.1.1

Published

An NPM module to register and get variable can used in both nodeJS and mini-program

Downloads

5

Readme

universal-env

An NPM module to register and get variable can used in both nodeJS and mini-program

Install

npm install uni-envs

Usage

env.js

import Envs from 'uni-envs'

/**
 * We recommend you do this to avoid typo
 */
const ENV_KEY_DEBUG = "DEBUG"
const ENV_KEY_DB_URI = "DB_URI"
const ENV_KEY_VERSION = "VERSION"

/**
 * Init Envs
 */
Envs.init()

/**
 * Envs will load from process.env and throw an error if it's not provided.
 * ( We assume DEBUG=True )
 */
Envs.register(ENV_KEY_DEBUG)

// ... and get by this 
// (You can set the `type` option to `"boolean"` to let get() return a boolean)
Envs.get(ENV_KEY_DEBUG)
// > "True"
Envs.getByString(ENV_KEY_DEBUG)
// > "True"
Envs.getByBoolean(ENV_KEY_DEBUG)
// > true

// Uncomment the line below will throw an error because you register the same key twice.
// Envs.register(ENV_KEY_DEBUG)

/**
 * You can also give it a default value to avoid the error
 */
Envs.register(ENV_KEY_DB_URI, "mongo://Some.Default.URI")


// It also support number, boolean and json (json need to set the type)

Envs.register(ENV_KEY_VERSION, 3)
// will auto trans to the number: 3
Envs.get(ENV_KEY_VERSION)
// > 3

Envs.register("JSON", { default: { someJSON: 123 }, type: "json" })
Envs.get("JSON")
// > { someJSON: 123 }
/**
 * It's fine to set different value for different environment.
 * (NODE_ENV = develop / staging / release(production) )
 */
Envs.register("MONGO_DB_URI", { 
  develop: "mongo://Some.Default.URI/develop",
  staging: "mongo://Some.Default.URI/staging",
  release: "mongo://Some.Default.URI/release"
})

// another way to avoid the error
Envs.register("SOMETHING_OPTIONAL", { require: false })

//