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 🙏

© 2025 – Pkg Stats / Ryan Hefner

oorjs

v0.0.1

Published

Environment variable manager for development

Readme

oorjs

oorjs is a simple library to maintain environment variables in development cycle. It is also able to differentiate between development and production environment based on presence of json profile file.

Usage

A simple use case for this library would be

require('oorjs')('.env',function(flag){
  console.log("KEY :"+process.env.key);
});

where .env file is a json file that contains profile for the environment. The second callback function has a flag set to true if production environment is in development.

Creating a profile

oorjs can use multiple separate profile that can be selected at runtime. A sample json file is

{
	"Profile 1": {
		"key": "12sdf3",
		"server": "8723"
	},
	"Profile 2": {
		"key": "123",
		"server": "8723"
	}
}

What changes to make in production environment

None whatsoever. If the environment file in this case .env file is missing, it automatically assumes running in production environment. All you are left with is to set production variables and you are done. Remember the local environment file that stores all the profiles should be added in .gitignore before pushing the codes.