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

layer

v0.1.0

Published

transparently proxies functions, objects

Downloads

320

Readme

Build Status

layer

Unobtrusive transparent proxies with very little setup. Doesn't require re-writing existing code. You can just drop it right in!

Runs anywhere there's javascript (browser & node).

--> (layer) --> (function/object)

// add a simple proxy without modifying any existing code!
var addBig = function(x, y, next) { 
  x = x * 100;
  y = y * 100;
  next(x, y);
}

var that = this;
layer.set(that, add, addBig);

// existing code...
function add(x, y) {
  return x + y;
}

add(2, 2); // 400

And that's it, all instances of calling add() in your existing code now go through addBig() then add()

You don't re-write your code! Or have to call addBig() directly.

(Note: this won't work in node.js because add is private, see here.)

For some fun stuff you can do with layer, check out intercept.js.

Usage / API

Setting a proxy

layer.set(context, function to proxy, proxy function)

Context being scope or this, read more about it here.

In the browser when you set 'null' as the context, it'll default to global (browser only).

Unsetting a proxy

layer.unset(func) or following the example: layer.unset(add)

Skipping your proxy

For those times when you want turn skip a layer...

func.skip() or following out add example add.skip(2, 2)

Replacing not proxying (monkey patching)

layer.replace(context, function to replace, new function)

Stopping a proxy early

At anytime you may stop early by not calling next.

And either call your callback (async) or return (sync);

Install

  • node: npm install layer

  • browser: use layer.min.js

Some advice on knowing the context.

(You can't proxy private variables!)

Because they're private. Not a big deal, and it's obvious enough. But keep in mind that in a node.js, the root of the module all your var's are effectively private (so the readme example above will not work).

Work around would be exports.add and the context being 'exports' would work. Or if add was in an object var obj = { add: ... }, context being 'obj'.

(Basically, it works like normal except for private variables.)

Some more examples:

var somelib = require('somelib'); 
layer.set(somelib, somelib.func, proxyFn)
function Cat() {}
Cat.prototype.meow = function() {...}

layer.set(Cat.prototype, Cat.prototype.meow, proxyFn)