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

wspr

v2.2.0

Published

WebSocket proxy for post http requests. Perfect for testing purposes/mocks

Downloads

1,008

Readme

styled with prettier PRs Welcome

WSPR

WebSocket proxy for post http requests. Perfect for testing purposes/mocks 🚀

wssExample

Installation

npm i -g wspr

Usage

Just run

wspr

after, you will see output with 2 urls:

WebSocket server started ws://localhost:3005
HTPP proxy server started http://localhost:3006

Broadcast message to clients:

To broadcast message to clients send a post requests with a string/json body (via postman or curl) to http enpoint provided on the previous step.

curl -d "{"hello": "world"}" -X POST http://localhost:3006

Websocket over secure connection

If you want to run the websocket server over a secure connection, follow these steps:

  1. create self signed certificates: https://letsencrypt.org/docs/certificates-for-localhost/#making-and-trusting-your-own-certificates

  2. trust the self signed certs, eg on mac: https://tosbourn.com/getting-os-x-to-trust-self-signed-ssl-certificates/

  3. pass the paths to the certificate and key using the --cert and --key CLI args, eg:

wspr --cert=./localhost.crt --key=./localhost.key
  1. you should see the websocket is now running over wss:
WebSocket server started wss://localhost:3005

Enjoy 🚀🥤