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

message_xpress

v0.1.4

Published

middleware framework for amqp messages

Downloads

4

Readme

messageXpress

Fast, unopinionated, minimalist amqp framework for Node.js. raw message arrived from amqp is wrapped as an http.IncommingMessage, this will help to use 99% of express middlewares already packages

all behavior will act the same as we expect from express framework; because middleware function has the same argument as express, we can handle the same middlewares and the same flows for each route

async / sync

fully support for async middlewares and sync middlewares

error handling

fully support for thrown exception inside middleware. app.use((req, res, next) => { next(throw new Error('this is the end')); })

route.use((req, res, next) => { // this will triggers only for [YOUR_QUEUE_NAME] route next(new Error('this is the end')); })

example

` const app = new Application();

app.use(express.json({limit: '50Mb'})); // this will triggers for all arriving messages

const route = new RouteLayer([YOUR_QUEUE_NAME]);

route.use((req, res, next) => { // this will triggers only for [YOUR_QUEUE_NAME] route next(); })

route.action([ACTION_NAME], (req, res, next) => { console.log(req.body); // will pring the message arrived from amqp next(); }, (req, res, next) => { res.json({success: true}); })

`

listeners

all listeners is sent as a reference

app.on('message_arrive', (rawMsg, ch, req) => { // TODO: what ever you want });

app.on('handled', (req, res) => { // TODO: all data sent with res.json will be waiting in res.body; });

app.on('error', (err: Error, req) => { // TODO: err can be of any type extends Error. // this is the error middleware is sending })