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 🙏

© 2024 – Pkg Stats / Ryan Hefner

assert-exists

v1.0.4

Published

A small package for consistently asserting if a value exists

Downloads

1,495

Readme

Assert Exists

Travis Build XO code style

A package for consistently asserting if a variable exists.

Usage


  1. Install. npm install assert-exists --save

  2. Use it.

var a = require("assert-exists");

var errorMsg = a.msg("MyPackage");

function MyPackage(options) {
  a.exists(options, errorMsg('options'));
  a.exists(options.someString, errorMsg('someString'), 'string');
}

Definition


  • .exists(value, errorMessage, *type)
    • Checks to see if value is not null, AND typeof type (if it's provided), otherwise throws AssertionError: "errorMessage".
  • .msg(packageString)
    • Returns a function that takes one argument and returns a string like:
"ERROR: Expected {1} to be passed into {packageString}."

Why


When passing configs into constructors, I ran into a problem where the same code was copied and pasted lots of times. That was annoying, verbose and error prone. It looked like this:

function MyPackage(configs) {
  assert(configs, "Expected configs to be passed into MyPackage");
  assert(
    typeof configs.enabled === 'bool',
    "Expected configs to be passed into MyPackage" // not correct
  );
  this.enabled = configs.enabled;
  
  assert(
    configs.db && typeof configs.db.host === 'string',
    'Expected host to be passed into MyPackage' // not really correct
  );
  assert(
    configs.db && typeof configs.db.port === 'string',
    'Expected host to be passed into MyPackage' // wrong string
  );
}

This sucks. So, I made the package to constrict my ability to mess this stuff up, and take away some of the copy-pasta incentive.

Now we have one function to check if it exists, and one to get an error message. Simple.


a.exists(finished, a.msg('README')('finished'), 'bool');