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

proxytron

v1.0.5

Published

Event proxying for Node EventEmitters with emphasis on reliability (100% test coverage) and readability (proxying needs to be clear). Zero dependencies, ES5+

Downloads

16

Readme

Proxytron

Build Status Latest Stable Version Test Coverage

proxytron provides proxying between NodeJS EventEmitters. Zero dependencies, ES5+, browser support via browserify or EventEmitter shim.

Goals

  • reliability - the library has 100% statement/branch coverage + type checking via flow
  • API readability - proxying needs to be clear as it's potentially confusing

## Example

// es6 example, proxytron works fine in es5 (or browser via browserify)
const proxy = require("proxytron");
const EventEmitter = require("events").EventEmitter;

const one = new EventEmitter;
const two = new EventEmitter;

// proxy API emphasises explicitness, so it's clear
// where events are proxied from and where they're going
const deproxy = proxy.all({
  from: one,
  to: two,
});

two.on("A", function(message) {
  console.log("heard A proxied with message '" + message  + "'");
});

one.emit("A", "proxied");

deproxy();

// this will not cause an event to be emitted from two as we've deproxied
one.emit("A", "again");

Installation

npm install --save proxytron

## API

proxy({ from: EventEmitter, to: EventEmitter, events: { [sourceEvent: string]: targetEvent }}): deproxyFunction

Proxies all events in the events object that are emitted on from. They will be re-emitted with all arguments on the emitter to.

Provide null or undefined as the targetEvent to reuse the original event name, or provide a string to rename the event that will be emitted from to.

Call the returned deproxyFunction to stop proxying.

proxy.all({ from: EventEmitter, to: EventEmitter, rename: { [sourceEvent: string]: targetEvent }}): deproxyFunction

Proxies all events emitted by from, meaning they will be re-emitted with all arguments on the emitter to.

Provide a string as the targetEvent in rename to rename event that will be emitted from to.

Call the returned deproxyFunction to stop proxying.

Contributing

Contributors welcome! Open up a PR and I'll make you a contributor.

Look at the package.json for how to run tests/typechecks etc.