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

wspost

v0.1.2

Published

Broadcasts data received via HTTP POST to all clients connected to Web Sockets

Downloads

2

Readme

wspost is stupid simple HTTP POST -> WebSocket gateway. It's using JWT authorization, but doesn't store any data.

Installation

npm i wspost -g

Generating channel token

You need to define your secret key and generate first channel token. You can set it in ENV or in app parameter.

export SECRET_KEY='< change me >'
wspost --gentoken example

Token can be also easily generated in third party app running on different server and written in other language. The only thing you will need are:

{
  "channel": "example"
}

Starting a server

There is only one port open for both, HTTP POST and WebSocket communication. By default it listens on port 3000, bout you can change it form command line or ENV variable PORT.

export SECRET_KEY='< change me >'
wspost --listen

Sending a message

Message delivery can be easily tested with cURL.

Try to open localhost:3000/example.html in your browser and wait for a message.

Token which you generated before is used as endpoint URL.

TOKEN=$(wspost --gentoken example)
curl -d something=123 localhost:3000/broadcast/$TOKEN