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

middleman

v0.1.0

Published

A small library that lets you inject some code between a third party library and the execution context. With **Middleman.js** you can easily:

Downloads

15

Readme

Middleman.js

A small library that lets you inject some code between a third party library and the execution context. With Middleman.js you can easily:

  • filter arguments passed to an original method,
  • pass one function's arguments to another function, or
  • overload a third party method to change how it works

Links

Example

Let's say you add a third party library to your application that has a method called doSomethingCool.

    var ThirdPartyLibrary = {
        doSomethingCool : function(firstParam, isAwesome) {
            // do something cool with firstParam, then:
            if (isAwesome){
                console.log('All up in your app, doing awesome things.');
            }
        };
    };

You decide that you want to force the second parameter isAwesome to be true every time doSomethingCool is called because your application is totally awesome. You could just write a wrapper method like this:

    var AwesomeApplication = {
        doSomethingCool : function(firstParam) {
            return ThirdPartyLibrary.doSomethingCool(firstParam, true);
        }
    };

    AwesomeApplication.doSomethingCool('blah blah blah');
    /**
     * console: All up in your app, doing awesome things.
     */

However, now you have to remember to call your method instead of the original method. What if ThirdPartyLibrary is very popular (e.g. jQuery)? Your colleague Tony has been using ThirdPartyLibrary for years. He doesn't remember to use your wrapper function when writing new code for your application.

Middlman.js gets between Tony and ThirdPartyLibrary, so your application stays awesome. :expressionless:

    var MM = new Middleman();

    MM.map({
        lib : ThirdPartyLibrary,
        method : 'doSomethingCool',
        filter : function(args) {
            // make the second parameter true
            args[1] = true;
            return args;
        }
    });

    ThirdPartyLibrary.doSomethingCool("I'm Tony, and the second param is undefined.");
    /**
     * console: All up in your app, doing awesome things.
     */

Piece of cake.