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

alton

v0.1.3

Published

a config object module

Downloads

8

Readme

Alton

Install

npm install alton

Schema

schema are multi-level structure defined by an object as following

const Alton = require("alton");

const mySchema = new Alton({
  env: {
    default: "development", // !! required !! (set this as null or smth if you don't want to provide a default value)
    format: "string", // see formats below
    env: "NODE_ENV", // any env var to load for this options
    // env could also bee and array in this case leftmost is tried first
    // but if it's not found the one at its right is tried next and over and over ...
    // env : ["NODE_ENV","ENV"]
    doc: "Set node env" // currently not doing anything with that but this will come one day on another
  },
  netsted: {
    // alton is multi-level it will detect as an options anything that has a "default prop"
    netstedA: {
      default: true,
      format: "boolean"
    },
    netstedB: {
      default: 74
      // if omitted, format is set as "any"
    }
  }
});

Format

formats allows you to check an option validity and add support for coercion

Alton.registerFormat("port", {
  // validate is a method that is called in order to ensure that a value matches a format
  // this method must throw an error if the value is incorrect
  validate(val) {
    if (Number.prototype.toString.call(val) !== val.toString())
      throw new Error("port must be a number");
    if (Math.floor(val) !== val)
      throw new Error("port number must be an integer");
    if (!(0 <= val && val <= 65535))
      throw new Error(`${val} is not a valid port number`);
  },
  coerce(val) {
    // val comes from an env var so it's a string here let's convert it to a number
    return Number(val);
  }
});

You can also register anonymous formats directly in you schema definition

let mySchema = new Alton({
  port: {
    default: 7474,
    format: {
      validate(val) {
        // validation stuff here...
      },
      coerce(val) {
        return Number(val);
      }
    }
  }
});

:warning: validate method must be synchronous for now