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

optionally

v0.1.3

Published

Option parser with schema definition and descriptive errors

Readme

optionally npm install optionally gzip size dependencies

Option parser with schema definition and descriptive errors:

const schema = {
  port: { default: 3000, type: Number },
  public: { default: "public", type: [String, Boolean] }
};

// All of these result in `{ port: 3000, public: "public" }`
optionally(schema);                   // Uses the defaults
optionally(schema, { port: "3000" }); // Cast to a number since it's possible
optionally(schema, {}, process.env);  // `.env` is `PORT=3000`

// Clear error messages:
optionally(schema, { port: "cow" });
// TypeError: The option `port` should be a number like `{ port: 3000 }` instead of the string "cow".

The arguments for each of the options, with all of them being optional:

|key |description |type | |------------|-----------------------------------------|-----------------------| |find() |manually get the value from the params |function | |↳ env |name of the environment variable to use |string | |↳ arg |name of the argument to use |string | |↳ inherit |for subtrees, get the value from parent |boolean, string | |↳ default |value to use if none is provided |any | |parse() |parse the previously found value |function | |↳ extend |extend the default object with the value |boolean | |validate()|manually check that the value is correct |function | |↳ type |type must match (or cast) to one of these|function, string, array| |↳ required|value must be provided and found |boolean | |↳ enum |it has to match exactly one of these |array | |options |define the schema of the children |object |

Internally it works in three steps, if you provide the main function then it will not perform the other actions:

  • find(): uses env > arg > inherit > default (in order) to attempt to get a value out of the arguments and environment.
  • clean(): uses extend, file and folder to expand the previously found value.
  • validate(): uses type, required, enum,

Helpers:

  • __root: "abcdef": if a single option is provided that is not an object, it will be converted into { abcdef: options }. Example: accept a port as a single argument { __root: "port" } + server(3000) = server({ port: 3000 }).
  • __mode: "strict": defines what to do with options that are not defined. "strict" will throw with keys that are not in the schema, "remove" will delete these extra keys and "flexible" will pass through any extra arguments.