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

elc-typey

v0.1.0

Published

some kind of slightly awful runtime type checking helpers

Downloads

8

Readme

ELC-TYPEY

Some helpers and bits 'n' bobs for runtime type checking.

You'll probably never want to use this library unless you have some very wierd and specific legacy/refactoring to do.

If you are using this on a brand new project you should probably look at ES7 decorators or sweet-js macros instead.

Usage

var type = require('elc-typey');

var typeCheck = type(constructor || "string" || undefined [, ...]);

var stuff = function(user, name, age){
  typeCheck(arguments);
}

type takes a variable number of arguments, each of which should either be a

  • constructor function : if supplied then an instanceof test will be used.
  • string : if supplied then a typeof test will be used and compared against the supplied string.
  • undefined || "*" : if supplied then no type checking will be used.

The function returned by type() should then be called with the arguments you wish to type check.

elc-typey exports some aliases to shorten function signatures

var type = = require('elc-typey');

console.log(type);
{ [Function: typeCheck]
  fn: 'function',
  str: 'string',
  bool: 'boolean',
  num: 'number',
  obj: 'object',
  any: '*'
}

var typeCheck = type(type.fn, type.bool, '*')

This library will not modify the arguments in anyway before passing them through to your original function. (combinators are great things) (except ycombinator - that is a bad thing™)

Examples


type = require('elc-typey')

class Accounts

    constructor: type(Date, Date) (start, end)->

        @_start = somethingCool(start)
        @_date = somethingElseCool(end)
var type = require('elc-typey');

var User = function User();

var typeCheck = type(User, Date)

var myPlainFunction = function(user, date){
    //some logic and stuff
}

var typeCheckedFunc = typeCheck(myPlainFunction);

// this won't throw
typeCheckedFunc(new User(), new Date());

// this will throw
typeCheckedFunc('cat', new Date());
// throws : "Argument at position 0 was instance of 'String' but expected 'User'"