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

@themrdev/dotio

v1.0.0

Published

DotIO config manager

Readme

dotio

DotIO config manager

Why use DotIO?

  • Fast
  • Manage all configs in one file (per project)
  • Easy to use

Install for use on a module

Firstly, install the module, of course!

Next, create a .iom.yml (stands for iomanager)

Inside the .iom.yml add the following config

module: true
config: 
  - myConfigValue:
    expect: string
    optional: false # if optional is not specified, it defaults to false
  - myOtherValue:
    expect: '*' # doesn't matter whats inputted
    optional: true # optional
    defaultTo: 'wow default!!!!' # only happens if it config is optional & nothing is inputted

Next step, go into your main code and import the module

const { Module } = require('dotio');
// or: 
import { Module } from 'dotio';

new Module('./path-to-iom.yml');

Once done, you're all set, get config like so:

const { Get } = require('dotio');
// or:
import { Get } from 'dotio';

const myOtherValue = Get('myConfigValue');

Using it as a module-user

Step 1: Make sure the module you are using has dotio as a dependency & a iom.yml

Step 2: Create a config.io

Step 3: Write your config

This example uses how we set it up earlier with the module.

{global:cjays} = whatever this is
{myConfigValue} = Hello, you are using io with {cjays}

{myOtherValue} = [{cjays}, {myConfigValue}, hello]

Using this mechanic, the owner of the modules can't get global variables. However, you can use them. If someone got myConfigValue they'd see 'Hello, you are using io with whatever this is' and myOtherValue would be ['whatever this is', 'Hello, you are using io with whatever this is', 'hello']

Errors

Errors are thrown for everything, invalid types, not specifying required things and much more

In depth: Global variables

You can specify if you want the module to be able to see your global variables by adding at the top:

{GlobalVarsSeen} = true
...config

Comments

You can add comments like so:

...config
/# Hi, this is a comment!
/# This is another comments

Note that comments can only go on new lines!