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

@hitchy/plugin-socket.io

v0.1.1

Published

integrating socket.io server with Hitchy framework

Downloads

27

Readme

@hitchy/plugin-socket.io

integrates socket.io server with Hitchy framework

License

MIT

Installation

npm i @hitchy/plugin-socket.io

Usage

The websocket server of socket.io gets automatically integrated with Hitchy on next start of application. The server instance is exposed as api.websocket.

Hitchy's official features are exposed in namespace /hitchy.

Request handling

Hitchy starts listening to connected websocket clients emitting request messages describing requests to be dispatched mostly equivalent to the way regular HTTP requests to Hitchy are handled. Using the websocket is performing slightly better than separate HTTP requests.

On a client, you can use it like this:

io( "/hitchy" ).emit( "request", { 
    method: "POST",
    url: "/api/foo?q=bar",
    headers: { 
        // put request headers here
    },
    body: { 
        // provide some object with your payload data 
    },
}, ( { statusCode, headers, body } ) => {
    // TODO: handle the response
} );

Providing an object as request body is the preferred way. It gets implicitly serialized as JSON body on dispatching the request on server side. The content-type request header may be omitted and must not be set to anything but text/json or application/json. You can also provide a string or ArrayBuffer, in which case any custom content-type request header can be provided, too.

The response body may be data already parsed from a server-side JSON-response.

Custom application: handle requests

On server-side, you can have a service including code like this:

api.websocket.on( "connext", socket => {
    socket.on( "some-request", ( data, response ) => {
        // TODO process `data`, calculate `result`
        
        response( result );
    } );
} );

On client side, you can use that like this:

socket.emit( "some-request", data, result => {
    // TODO process the result
} );

Custom application: respond to server notifications

On server-side, you can emit broadcast notifications like this:

api.websocket.emit( "some-update", data );

On client side, you can receive these notifications like this:

socket.on( "some-update", data => {
    // TODO process the data
} );