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

envisor

v0.1.0

Published

Universal library for managing your environment variables

Downloads

5

Readme

envisor

npm version badge Build Status License

Universal library for managing your environment variables

Environment variables are a set of dynamic named values that can affect the way running processes will behave on a computer. They are part of the environment in which a process runs

License

MIT

Installation:

npm install envisor --save-dev

Usage

For example you could use the following code:

var env = require('envisor');

env.set('foo', 1);
env.get('foo'); // 1

API

.set

Sets/retrieves an environment variable

Primitive values

var env = require('envisor');

env.set('foo', 1);
env.get('foo'); // 1

Object values

var env = require('envisor');

env.set('foo', { bar: 1});
env.get('foo).bar; // 1

Object key/values

var env = require('envisor');

env.set({ foo: 1 });
env.get('foo'); // 1

.has

Checks an environment variable

var env = require('envisor');

env.set('foo', 1);
env.has('foo'); // true

.use

Use you personal namespace

var env = require('envisor');

env.use('foo');
env.set('bar', 1);
env.get('foo'); // 1
process.env.foo_bar; // 1

.remove

Removes an environment variable

var env = require('envisor');

env.set('foo', 1);
env.remove('foo');
env.get('foo'); // ''

.all

Returns all environment variables

var env = require('envisor');

env.all(); // process.env

Tests

npm test

Links

Environment variables process.env

Task submitted by Alexander Abashkin