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

sukka

v0.0.1

Published

WebSocket testing made easy

Downloads

1

Readme

Sukka

🧦 WebSocket testing made easy

Setup

Install Sukka and add it to your package.json file:

yarn add sukka --dev

Usage

Example WebSocket test using Jest:

const connect = require("sukka");

test("Login replies with a welcome message", () => {
  return connect("http://localhost:3000")
    .emit("login", "Foo")
    .expect("welcome", res => expect(res).toEqual("Bar"));
});

This test will:

  1. Attempt to connect a WebSocket to localhost:3000.
  2. Emit a single message with "login" as event name and "Foo" as the payload data.
  3. Wait for a message to be received with "welcome" as event name.
  4. Assert that the received message contains "Bar" as the payload data.

API

.emit(eventName[, ...args])

Emits an event to the endpoint with the provided name and arguments.

.expect(eventName[, handler])

Waits for a single event with the provided name. If a handler is provided, it will be called with the payload from the received message.

.end(callback)

Calls callback with an error as the first argument if some expectation failed. Use this to complete the test case and report the result back to your testing framework (typically done by passing the done handler as the callback).