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

env-variable

v0.0.6

Published

Cross platform environment variables with process.env, window.name, location.hash and localStorage fallbacks

Downloads

2,205,285

Readme

env-variable

A cross platform env-variable for browsers and node. Of course, browsers doesn't have environment variables but we do have hashtags and localStorage which we will use as fallback.

hashtags

This is a really easy way of adding some trigger some environment variables that you might use for debugging. We assume that the hashtag (#) contains a query string who's key is the name and the value.. the value.

localStorage

If you want more persisting env variables you can set a query string of env variables in localStorage. It will attempt to use the env variable.

Installation

This module is written for node and browserify and can be installed using npm:

npm install --save env-variable

Usage

This module exposes a node / module.exports interface.

var env = require('env-variable')();

As you can see from the example above we execute the required module. You can alternately store it but I don't assume this a common pattern. When you execute the function it returns an object with all the env variables.

When you execute the function you can alternately pass it an object which will be seen as the default env variables and all fallbacks and process.env will be merged in to this object.

var env = require('env-variable')({
  foo: 'bar',
  NODE_ENV: 'production'
});

Oh, in env-variable we don't really care how you write your env variables. We automatically add an extra lower case version of the variables so you can access everything in one consistent way.

And that's basically everything you need to know. random high fives.

License

MIT