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

wscli

v1.1.0

Published

CLI WebSocket client

Downloads

10

Readme

wscli

CLI WebSocket client

NOTE: Since this tool is intended to be used in development, it sets rejectUnauthorized option to false. It lets to bypass SSL Certificate checks when connecting to dev servers

Installation

npm install -g wscli

Usage

wscli HOST [COUNT=1] [MSG]
  • HOST: full path to websocket endpoint, e.g. ws://localhost:10000
  • COUNT: expected responses count (optional, defaults to 1).
    • COUNT=-1: wscli will keep listening forever
    • COUNT=0: wscli will connect and send message and ignore any incoming messages might be useful to test that connection is ok and there are no errors sending messages
  • MSG: optional message to send to server on connection

Examples

# Expect 1 message back and quit with exit code 0
wscli ws://localhost:10000 '{"action":"PING"}'
> {"action":"PONG","req":{"action":"PING"},"res":{"time":1496798038289}}
✔


# Expect 2 messages back and quit with exit code 0
wscli ws://localhost:10000 2 '{"action":"PING"}'
> {"action":"PONG","req":{"action":"PING"},"res":{"time":1496798038000}}
> {"action":"PONG","req":{"action":"PING"},"res":{"time":1496798039000}}
✔


# Listen forever, until interrupted
wscli ws://localhost:10000 -1
^C
✘-INT


# Any error, or server closes connection
14:14 $ wscli ws://localhost:10000 -1
Server has closed connection
✘-1

Timeout

By default wscli does not have any timeout, so if expected message never arrives, process will hang forever.

To avoid this issue, use timeout command like:

timeout 10 wscli ws://localhost:10000 -1

On MacOS you can install timeout as part of coreutils or use simple cross-platform replacement:

npm install -g @nkbt/timeout
timeout 10 wscli ws://localhost:10000 -1