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

rapport-router

v0.1.5

Published

Express style router plugin for Rapport

Downloads

17

Readme

rapport-router CircleCI Coverage Status

NPM

Express style router plugin for Rapport, intended for use with rapport-http.

Installation

Node: Install the plugin via NPM: npm install --save rapport-router

Browser: Attach rapport.router.min.js to your HTML page

Then add the plugin to rapport:

// Globally
Rapport.use(require('rapport-router')); // In Node.js
Rapport.use(RapportRouter); // In the browser

// Or to a instance
Rapport(wsImplementation).use(require('rapport-router')); // In Node.js
Rapport(wsImplementation).use(RapportRouter); // In the browser

Usage

This plugin adds a method to the global Rapport constructor. To create a new router, simply call it:

const router = Rapport.Router();

Once you have a router, usage is similar to express.js:

// Add a get route for /users
router.get('/users', (req, res, next) => {
    res.status(200).send({
        users: []
    });
});

// You can nest routers
const userRouter = Rapport.Router();
const mainRouter = Rapport.Router();
userRouter.get('/users', () => {});
mainRouter.use('/v1', userRouter); // The exposed route is now /v1/users

// Or add middleware to all routes
router.use((req, res, next) => {
    console.log('Got a request'); 
});

// Regex is supported
router.get('/user/:id', (req, res, next) => {
    console.log(req.params.id);
});

// Route arrays and multiple handlers are also supported
router.get(['/users', '/people'], () => {}, () => {}); // For routes
router.use(() => {}, () => {}); // For middleware
router.use(['/v1', '/v2'], router1, router2); // And for routers

// Handler arrays are flattened recursively. Thus, the following two lines are equivalent
router.use('/v1', [() => {}, () => {}], () => {});
router.use('/v1', () => {}, () => {}, () => {});

// Returning a promise calls next automatically when the promise resolves
router.get('/user', 
    (req, res) => {
        return Promise.resolve();
    },
    (req, res) => {
        res.status(200).send({
            users: []
        });
    });

// You can add also add a error handler to all routes
router.error((err, req, res, next) => {
    
    // Explicitly try-catch when you send the response in your final error handler, to handle cases when the websocket 
    // is closed while handling the request.
    try {
        res.status(500).send('Something went wrong :(');
    } catch (err) {
        console.log('Failed to send the error response:', err);
    }
});

Once a router has been created, you can add it to the Rapport websocket:

// To just the specific websocket
Rapport(wsImplementation).create('url', { router: router }); // Or
Rapport(wsImplementation).wrap(existingSocket, { router: router });

// Or to all the sockets created by the Rapport instance
Rapport(wsImplementation, { router: router }); // Or
Rapport(wsImplementation).configure({ router: router });

// Or to all sockets created by all Rapport instances
Rapport.configure({ router: router });