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 🙏

© 2026 – Pkg Stats / Ryan Hefner

config-tiny

v1.0.8

Published

A mimimal implementation of the popular config library. It can be used to saving environment variables.

Readme

CONFIG TINY :blush:

A personal implemention of the popular config library on NPM

Quick Start

npm i config-tiny

or

yarn add config-tiny

You can also fork the project on github at https://github.com/iamnasirudeen/config.tiny

Usage

Create a config folder in the root directory of your project and create a file inside the folder named default.json.

e.g

cd `path/to/project/` && mkdir config && cd config && touch default.json

The code above helps you create a config folder and also a default.json file inside the folder then you can use it like this.

The content of the default.json file should look like the one below.

{
  "data": {
    "email": "[email protected]"
  },
  "github_handle": "iamnasirudeen",
  "port": 3000
}

Then

const config = require("config-tiny");
let port = config.get("port") || process.env.PORT;

You can also check the validity of a string before getting the value using the config.has function. e.g

const config = require("config-tiny");

// Note: config.has function returns a boolean of true/false

// using ternary operator
const port = config.has("port") ? config.get("port") : 3000;

// using if statement
if (config.has("data.email")) {
  // do anything with your value here
  let email = config.get("data.email");
}

Note

The Config folder has to be in the root directory of your project as config uses the nodejs process.cwd() API to locate the root directory of the config folder.

config.tiny doesnt really support nested objects a future version would have this feature supported.

e.g

config.get("data.email"); // [email protected]
config.get("data"); // {email: "[email protected]"}
config.get("github_handle"); // iamnasirudeen

Use Case

config.tiny can be used to save environment keys. It can be used in replace of DotEnv.

Contributors are also allowed. You can hit me up at [email protected].

Developed with :heart: by Olohundare Nasirudeen https://github.com/iamnasirudeen