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

proving

v0.1.0

Published

Validate then throw.

Downloads

1,409

Readme

proving

A very simple type checking helper.

Table of Contents

  1. Overiew
  2. Installation
  3. Usage
  4. APIs

1. Overview

When I was doing many type checking for function arguments, I found myself doing a lot of if (type_not_met) throw new TypeError(msg) to make assertions. That's why I collect all these simple checkers together to be DON'T REPEAT YOURSELF as well as to help myself lower down line-of-codes.

Only 56 LOC to meet my daily use.

2. Installation

$ npm install proving --save

3. Usage

Here is a quick example, it's very very simple.

var proving = require('proving');
function myFunc(foo, bar) {
    proving.number(foo, 'foo should be a number.');
    proving.string(bar);    // this will throw will a default message
    // ...
}

myFunc(20, 'hello');    // not throw

myFunc('x', 'hello');   // throw TypeError('foo should be a number.')

myFunc(20, {});         // throw TypeError('Input value should be a string.')

4. APIs

.defined(val[, msg])

Throw if val is undefined.
Default message: 'Input value should be given.'

.string(val[, msg])

Throw if val is not a string.
Default message: 'Input value should be a string.'

.number(val[, msg])

Throw if val is not a number. Also throw if val is NaN.
Default message: 'Input value should be a number and cannot be a NaN.'

.boolean(val[, msg])

Throw if val is not a bool.
Default message: 'Input value should be a bool.'

.array(val[, msg])

Throw if val is not an array.
Default message: 'Input value should be an array.'

.object(val[, msg])

Throw if val is not an object. Also throw if val is NaN or null.
Default message: 'Input value should be an object.'

.fn(val[, msg])

Throw if val is not a function.
Default message: 'Input value should be a function.'

.stringOrNumber(val[, msg])

Throw if val is not a string nor a number.
Default message: 'Input value should be a number or a string.'