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

@tandem/mesh

v1.0.32

Published

Temporary directory for the updated version of [Mesh](http://mesh.js.org/).

Downloads

15

Readme

Mesh is a messsage routing library based on the stream standard.

This library will eventually be moved here after it becomes a bit more stable.

This library is intented to be more of a utility belt (like underscore, or lodash) for creating your own messaging routers. The docs here (still WIP) also serve as a guide to help you come up with messaging APIs, and patterns that are consistent across your codebase.

Motivation

Mesh was created to normalize how an application sends & receives messages throughout the application, and to other connected services over protocols such as HTTP, TCP, websockets, and others.

Mesh routers are also built to be composable - you can combine, mix & match them to create data flows according to your application needs. For instance, suppose you're using this library to handle HTTP requests:

import { IBus, DuplexStream } from "@tandem/mesh";

class HTTPRequest {
  
  constructor(readonly pathname: string, readonly ipAddress: string) {
  
  }
}

class RouterBus implements IBus {
  private _routes: {
    [Identifier: string]: IBus
  };
  constructor() {
    this._routes = {};
  }
  register(pathname: string, bus: IBus) {
    this._routes[pathname] = bus;
  }
  dispatch(request: HTTPRequest) {
     const route = this._routes[request.pathname);
     return route ? route.dispatch(request) : throw new Error(`Route "${request.pathname}" does not exist.`);
  }
}


const httpBus = new HTTPRouteBus();
httpBus.register("/home", {
  dispatch(request: HTTPRequest) {
    return new DuplexStream((req, res) => {
      res.write("hello world");
      res.close();
    })
  }
});

This is a start to an http router. There's still a ton of implementation that's required For this code to be used in production.

You can easily add a data throttling layer:

class ThrottleBus implements IBus {
   private _requests: {
    [Identifier: string]: number
   }
   constructor(readonly targetBus: IBus, readonly ttl: number) {
      this._requests = {};
   }
   
   dispatch(request: HTTPRequest) {
      const prevRequest = this._requests[request.ipAddress];
      if (prevRequest && prevRequest + this.ttl > Date.now()) {
        return throwEnhanceCalmError("Too many requests. Try again later.");
      }
      this._requests[request.ipAddress] = Date.now();
      return this.targetBus.dispatch(request);
   }
}

const httpBus = new HTTPRouteBus();

// 
let mainBus = new ThrottleBus(httpBus, 100);

Some missing things here, but shows composability of messaging routers.

This was added with very little modification to the application code. Suppose we want to pass the HTTP request over to a different application entirely:

TODO with socket.io bus, or sock bus.

Kitchen sink example

import { CallbackBus } from "mesh";

new CallbackBus()

new