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

enviro

v0.3.3

Published

env ===

Downloads

4

Readme

env

Env is a Node and client-side ~60 LOC library to manage what environment your code is running in, and let you override the environment for parts of the system.

Usage

On Node

Env = require('enviro')

Env.get('api') # Will return local, development, or production
Env.getInternal('api') # Will return local, qa, or prod

# Gets it's env from env vars, first would look to API_ENV, then NODE_ENV

On The Frontend

Enviro.get('usage_tracking')

# Set with window.USAGE_TRACKING_ENV or localStorage.USAGE_TRACKING_ENV

Functions

get(serviceName, [default]) - returns 'development' or 'production' to let you know which servers serviceName should be talking to

getShort(serviceName, [default]) - returns 'local', 'qa' or 'prod', otherwise the same as get

deployed(serviceName) - Returns boolean based on whether serviceName should be considered actually deployed

Deployed

By convention, the environments defined by specific names refer to which server you should be communicating with, not which environment this process is actually in. The special deployed env can be used to get the actual environment the process is running in.

Enviro also provides the deployed function which will return true if the service is deployed.

Manipulating Things

You can override what apis your software talks to, and whether it thinks it's deployed.

  • The env var / localstorage key API_ENV will, for example, change what is returned by Env.get('api')
  • The env var / localstorage key GAMERA_DEPLOYED will, for example, change what is returned by Env.deployed('gamera')
  • A request for Env.get('api.gamera') will first look to GAMERA_ENV, then API_ENV