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 🙏

© 2026 – Pkg Stats / Ryan Hefner

ezfn

v0.0.3

Published

EZFN ====

Downloads

5

Readme

EZFN

Are your functions professionally namespaced and difficult to reach? Would you like to kick back, throw caution to the wind, and call functions with the greatest of ease? EZFN is there for you.

Pollute the global namespace! Namespacing is a honking bad idea, let's do less of that!

Install

npm install --save ezfn

Usage

Here's a very smart example of making all p5 functions callable globally.

const ezfn = require("ezfn");
const p5 = require("p5");

ezfn(p5);

And here is a very foolish example of making all Array functions global.

const ezfn = require("ezfn");

ezfn([]);

API

EZFN only has one function. That function only has two arguments. Here they are.

  • src {Object} - the object with functions
  • dest {Object} [optional] - The destination object onto which src's functions are copied. It defaults to window because why would you not want to copy everything there?

Both own and inherited functions are copied.

Inspiration

p5 is the main inspiration. p5 is wonderfully approachable, in large part because every function is in the global namespace.

I wanted to preserve that, while also using p5 in an ES module.

Obviously, namespacing is a good idea.