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

sf-env

v1.0.1

Published

Log the current NODE_ENV, checking if it is supported in the application. If it's is not, overrides it with the default one.

Downloads

5

Readme

#Soluzioni Futura Enviroments


Log the current NODE_ENV, checking if it is supported in the application. If it's not, overrides it with the default one. Colors are from npm Colors, check the docs to see available ones.

1 - you can fully customize your environment set and the default environment if NODE_ENV is not set:

//setting up environment set
var environmentSet = {
 environments: {
   development: { color: 'green' },
   staging: { color: 'yellow' },
   production: { color: 'blue' }
 }
};

//requiring module and passing environment set and the default environment
require('sf-env')(environmentSet, 'staging');

2 - you can just customize the environment set without specifying the default environment (first one will be the default one):

//setting up environment set
var environmentSet = {
 environments: {
   development: { color: 'green' },
   staging: { color: 'yellow' },
   production: { color: 'blue' }
 }
};

//requiring module and passing environment set (default environment will be 'development')
require('sf-env')(environmentSet);

3 - you can use default environment set (by default the environmentSet object is equal to the example above) and specify only the default environment

//requiring module and passing default environment
require('sf-env')('development');

4 - you can use default environment set and first of them as default environment if NODE_ENV is not set

//requiring module and calling it with no arguments
require('sf-env')();