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 🙏

© 2026 – Pkg Stats / Ryan Hefner

weso-browser

v1.0.8-1

Published

Simple and light weight websocket client for the browser:

Downloads

47

Readme

weso-browser

Simple and light weight websocket client for the browser:

for more details on the protocol, checkout weso

`npm install weso-browser`

Usage example :

const weso = require('weso-browser')

const server = weso({
  url: 'localhost',
  port: 7266,
  retryDelay: 1000,
  publish: [ 'test' ],
  subscribe: [
    'initApps',
    'appDown',
    'appUp',
  ]
})

server.on.error(err => console.log('error', err))
server.on.close(err => console.log('close', err))

/*
  route = 'appUp',
  data = what ever the server sent
  ws = the websocket client instance
*/
server.appUp(({ route, data, ws }) => {
  console.log('yolo swag:', data, route)
  // send 'pouet' back to the websocket server on the route pouet
  server.test('pouet')
})

Shitty stuff :

You can init the server and start posting stuff synchronously, but it will silently ignore any message send before the server is started. So you better wait until the server is open.

Later on i may store all messages until the server is open, for now, just be aware of it.