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

@httptoolkit/websocket-stream

v6.0.1

Published

Use websockets with the node streams API. Works in browser and node, with all current WS versions

Downloads

2,150,736

Readme

websocket-stream Build Status Get it on npm

Part of HTTP Toolkit: powerful tools for building, testing & debugging HTTP(S)

Use HTML5 websockets using the Node Streams API.

This is a fork of the original websocket-stream (now unmaintained), for use in HTTP Toolkit. This fork:

  • Uses isomorphic-ws so that the 'ws' module is not loaded unnecessarily in browsers
  • Supports WS up to version 8 (note that isomorphic-ws uses * as its ws version, so this will always use the latest compatible release)
  • Fixes and extends the TypeScript types, and adds an explicit dependency on @types/ws
  • Has a CI build for automated testing
  • Adds a 'ws-close' event, which exposes the close event data when a websocket is closed by a close frame (before the stream 'close' event, which is different)

Usage

This module works in Node or in Browsers that support WebSockets. You can use browserify to package this module for browser use.

var websocket = require('@httptoolkit/websocket-stream')
var ws = websocket('ws://echo.websocket.org')
process.stdin.pipe(ws)
ws.pipe(process.stdout)

In the example above ws is a duplex stream. That means you can pipe output to anything that accepts streams. You can also pipe data into streams (such as a webcam feed or audio data).

The underlying WebSocket instance is available as ws.socket.

Options

The available options differs depending on if you use this module in the browser or with node.js. Options can be passed in as the third or second argument - WebSocket(address, [protocols], [options]).

options.browserBufferSize

How much to allow the socket.bufferedAmount to grow before starting to throttle writes. This option has no effect in node.js.

Default: 1024 * 512 (512KiB)

options.browserBufferTimeout

How long to wait before checking if the socket buffer has drained sufficently for another write. This option has no effect in node.js.

Default: 1000 (1 second)

options.objectMode

Send each chunk on its own, and do not try to pack them in a single websocket frame.

Default: false

options.binary

Always convert to Buffer in Node.js before sending. Forces options.objectMode to false.

Default: true

options.perMessageDeflate

We recommend disabling the per message deflate extension to achieve the best throughput.

Default: true on the client, false on the server.

Example:

var websocket = require('@httptoolkit/websocket-stream')
var ws = websocket('ws://realtimecats.com', {
  perMessageDeflate: false
})

Beware that this option is ignored by browser clients. To make sure that permessage-deflate is never used, disable it on the server.

Other options

When used in node.js see the ws.WebSocket documentation

On the server

Using the ws module you can make a websocket server and use this module to get websocket streams on the server:

var websocket = require('@httptoolkit/websocket-stream')
var wss = websocket.createServer({server: someHTTPServer}, handle)

function handle(stream, request) {
  // `request` is the upgrade request sent by the client.
  fs.createReadStream('bigdata.json').pipe(stream)
}

We recommend disabling the per message deflate extension to achieve the best throughput:

var websocket = require('@httptoolkit/websocket-stream')
var wss = websocket.createServer({
  perMessageDeflate: false,
  server: someHTTPServer
}, handle)

function handle(stream) {
  fs.createReadStream('bigdata.json').pipe(stream)
}

You can even use it on express.js with the express-ws library:

const express = require('express');
const expressWebSocket = require('express-ws');
const websocketStream = require('websocket-stream/stream');
const app = express();

// extend express app with app.ws()
expressWebSocket(app, null, {
    // ws options here
    perMessageDeflate: false,
});

app.ws('/bigdata.json', function(ws, req) {
  // convert ws instance to stream
  const stream = websocketStream(ws, {
    // websocket-stream options here
    binary: true,
  });

  fs.createReadStream('bigdata.json').pipe(stream);
});

app.listen(3000);

Run the tests

Server-side tests

npm test

Client-side tests

First start the echo server by running node test-server.js

Then run npm start and open localhost:9966 in your browser and open the Dev Tools console to see test output.

license

BSD LICENSE