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

args-filter

v1.0.3

Published

A javascript extention to the arguments prototype to inculde defaults and type checking in a cleaner faster manner

Downloads

12

Readme

Issue : needing to verify the parameters in javascript functions in an effective and clean manner.

Lets say we have the following function.

var foo = function(num){ return num / 3; }

We are assuming that num is a number, and currently we have no default values and no type checking so this will totally work foo({}) or foo(foo) or foo('anything') or even foo() and undefined / 3 is an error. This is a simple version of this but it shows the issue.

We have methods of overcoming this such as the following.

method 1

var foo = function(num){ if(num){ num = 1; } return num / 3; }

method 2

var foo = function(num){ num = num | 1; return num / 3; }

These methods do the same thing but what if num was 0 both would reassign it to 1 also if it is a string it would not catch this. This catches the edge cases and also verifies the type of data.`

method 3

var foo = function(num){ if(typeof num !== 'number'){ num = 1; } return num / 3; }

Do this methods scale well

var foo = function(num, str, arr, obj, func){ var boo = [] //holder for all values

if(typeof num !== 'number'){
	num = 1;
}
if(typeof str !== 'string'){
	str = '';
}
if(Array.isArray(arr)){
	arr = [];
}
if(typeof obj !== 'object'){
	obj = {};
}
if(typeof func !== 'function'){
	func = function(){};
}
boo.push(num, str, arr, obj, func);
return boo

}

This take a good chunk of code just to verify types and set defaults. What if we did the same code but this way

var foo = function(num, str, arr, obj,func){ arguments.types(1,'',[],{},function(){}); return arguments.toArray(); }

what if we didn't care about types we just wanted defaults just in case they were undefined.

var foo = function(num, str, arr, obj,func){ arguments.defaults(1,'',[],{},function(){}); return arguments.toArray(); }

This does convert the source variables so when you call num it will be num not arguments[0]

var foo = function(num){ arguments.defaults(1); return num + 1; }

var bar = function(num){ arguments.types(1); return num + 1; }

foo() would be 2 foo('') would be '1' bar() would be 2 bar('') would be 2