react-websocket 2.2.0 → 3.1.0

package/README.md

@@ -1,84 +1,168 @@
-# react-websocket [![contributions welcome](https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat)](https://github.com/mehmetkose/react-websocket/edit/master/README.md) [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fmehmetkose%2Freact-websocket.svg?type=shield)](https://app.fossa.io/projects/git%2Bgithub.com%2Fmehmetkose%2Freact-websocket?ref=badge_shield)
+# react-websocket
 
-`react-websocket` is a easy-to-use React component for websocket communications.
+**Hooks-first WebSocket client for React 18 and 19.** Shared connections, automatic reconnects, a send queue, typed and validated messages, and Suspense, in about 2.5 kB with zero dependencies.
 
-## Help Wanted
+[![npm](https://img.shields.io/npm/v/react-websocket.svg)](https://www.npmjs.com/package/react-websocket)
+[![CI](https://github.com/mehmetkose/react-websocket/actions/workflows/ci.yml/badge.svg)](https://github.com/mehmetkose/react-websocket/actions/workflows/ci.yml)
+[![bundle size](https://img.shields.io/bundlejs/size/react-websocket)](https://bundlejs.com/?q=react-websocket)
+[![types](https://img.shields.io/npm/types/react-websocket.svg)](https://www.npmjs.com/package/react-websocket)
+[![license](https://img.shields.io/npm/l/react-websocket.svg)](LICENSE)
+[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fmehmetkose%2Freact-websocket.svg?type=shield)](https://app.fossa.io/projects/git%2Bgithub.com%2Fmehmetkose%2Freact-websocket?ref=badge_shield)
 
-Things here are running very slowly as I have a lot of other stuff to take care at the moment so please don't be upset if I don't answer your question or if a PR sits unreviewed for a few days or weeks. Anyone interested in helping it move faster can help by submitting or reviewing PR's and answering each other's questions.
+**[Documentation](https://mehmetkose.github.io/react-websocket/)** · [Getting started](https://mehmetkose.github.io/react-websocket/guide/getting-started) · [API](https://mehmetkose.github.io/react-websocket/api/) · [Recipes](https://mehmetkose.github.io/react-websocket/recipes) · [Changelog](CHANGELOG.md)
 
+- **Shared connections.** Components using the same URL share one socket. StrictMode, `<Activity>` and route transitions never open duplicates.
+- **Auto-reconnect.** Exponential backoff with jitter, plus an immediate retry when the browser comes back online or the tab becomes visible. Optional heartbeats detect dead links.
+- **Send queue.** `send()` before the socket is open just works. The message goes out on connect.
+- **Typed messages.** `json: true`, your own codec, or validation with any [Standard Schema](https://standardschema.dev) library (zod, valibot, arktype), with inferred types.
+- **Suspense.** `use(client.ready)` waits for the first connection, and reconnects never flash a fallback.
+- **Topic subscriptions.** Reference-counted `subscribe`/`unsubscribe` messages that are sent again after every reconnect, so feeds don't silently stop.
+- **Message state.** Reduce messages into a store, and let each component re-render only when its slice changes.
+- **SSR-safe.** Never connects during a server render, hydrates cleanly, and ships a `'use client'` entry for Next.js and other Server Components frameworks.
+- **Small and typed.** Zero dependencies, ESM + CJS, TypeScript declarations with inline docs, plus a React-free `react-websocket/core` entry.
 
-### Installing
+## Install
 
+```sh
+npm install react-websocket
 ```
-npm install --save react-websocket
+
+## Quick start
+
+```tsx
+import { useState } from 'react';
+import { useWebSocket } from 'react-websocket';
+
+type ChatIn = { user: string; text: string };
+type ChatOut = { text: string };
+
+function Chat() {
+  const [messages, setMessages] = useState<ChatIn[]>([]);
+  const { status, send } = useWebSocket<ChatIn, ChatOut>('wss://api.example.com/chat', {
+    json: true,
+    onMessage: message => setMessages(list => [...list, message])
+  });
+
+  return (
+    <>
+      <p>{status}</p>
+      <ul>
+        {messages.map((m, i) => (
+          <li key={i}>
+            {m.user}: {m.text}
+          </li>
+        ))}
+      </ul>
+      <button onClick={() => send({ text: 'hi' })}>Say hi</button>
+    </>
+  );
+}
 ```
 
-### Usage
+Handlers always see your latest props and state, and changing them never reconnects. `send`, `close` and `reconnect` keep the same identity between renders.
+
+## Shared clients
+
+Define a connection once and use it anywhere, including outside React:
 
-```js
-  import React from 'react';
-  import Websocket from 'react-websocket';
+```tsx
+import { createWebSocket, useWebSocketEvent, useWebSocketStatus } from 'react-websocket';
 
-  class ProductDetail extends React.Component {
+export const chat = createWebSocket<ChatIn, ChatOut>('wss://api.example.com/chat', { json: true });
 
-    constructor(props) {
-      super(props);
-      this.state = {
-        count: 90
-      };
-    }
+function Messages() {
+  const [messages, setMessages] = useState<ChatIn[]>([]);
+  useWebSocketEvent(chat, 'message', m => setMessages(list => [...list, m])); // no re-render per message
+  return <ul>{/* … */}</ul>;
+}
+
+function Header() {
+  const status = useWebSocketStatus(chat); // re-renders only when the status changes
+  return <button onClick={() => chat.send({ text: 'hi' })}>Say hi ({status})</button>;
+}
+```
 
-    handleData(data) {
-      let result = JSON.parse(data);
-      this.setState({count: this.state.count + result.movement});
-    }
+The client connects when the first component uses it and closes a tick after the last one unmounts.
 
-    render() {
-      return (
-        <div>
-          Count: <strong>{this.state.count}</strong>
+## Suspense
 
-          <Websocket url='ws://localhost:8888/live/product/12345/'
-              onMessage={this.handleData.bind(this)}/>
-        </div>
-      );
-    }
-  }
+```tsx
+import { use, Suspense } from 'react';
 
-  export default ProductDetail;
+function Room() {
+  use(chat.ready); // React 19: suspend until the first connection
+  return <Messages />;
+}
+
+<ErrorBoundary fallback={<Retry onClick={() => chat.reconnect()} />}>
+  <Suspense fallback={<Spinner />}>
+    <Room />
+  </Suspense>
+</ErrorBoundary>;
 ```
 
-### Properties
+`ready` stays resolved through automatic reconnects, so a network blip shows your `status` UI instead of replacing the page with a spinner. It rejects if the client gives up or `close()` is called.
+
+## API at a glance
 
-#### url
+| Export | |
+| --- | --- |
+| `useWebSocket(url \| client, options?)` | Connect; returns `{ status, lastMessage, attempt, send, close, reconnect, client }` |
+| `useWebSocketEvent(client, type, listener)` | Handle `'open'`, `'message'`, `'close'` or `'error'` without re-rendering |
+| `useWebSocketStatus(client)` | The status; re-renders only when it changes |
+| `useWebSocketTopic(topics, topic)` | Hold topic subscriptions that survive reconnects |
+| `useWebSocketState(store, selector?)` | Read state reduced from messages; re-renders only when the selection changes |
+| `createWebSocket(url, options?)` | A shareable client: `send`, `on`, `connect`, `close`, `reconnect`, `ready`, `getSnapshot`, `subscribe` |
+| `createWebSocketTopics(client, { subscribe, unsubscribe })` | Topic subscription manager for `useWebSocketTopic` |
+| `createWebSocketState(client, { initialState, reduce })` | Message-state store for `useWebSocketState` |
+| `MessageError` | Reported to `onError` when a message fails `parse` or `schema` |
 
-**required**
-The url the websocket connection is listening to.
+| Option | Default | |
+| --- | --- | --- |
+| `protocols` | | Sub-protocols for the `WebSocket` constructor |
+| `binaryType` | `'blob'` | |
+| `json` | `false` | `JSON.parse` incoming and `JSON.stringify` outgoing messages |
+| `parse(data)` / `serialize(message)` | | Custom codec; takes precedence over `json` |
+| `schema` | | Standard Schema validation; types are inferred |
+| `reconnect` | `true` | `false`, or `{ maxAttempts, minDelay, maxDelay, factor, jitter, shouldReconnect }` |
+| `heartbeat` | | `{ interval, message, pong, timeout }` |
+| `queue` | `true` | `false`, or `{ limit }` |
+| `logger` | | e.g. `console.debug` |
+| `WebSocket` | global | Custom implementation for tests or Node |
 
-#### onMessage
+`useWebSocket` also takes `onOpen`, `onMessage`, `onClose`, `onError` and `enabled`. The [API reference](https://mehmetkose.github.io/react-websocket/api/) documents everything.
 
-**required**
-The callback called when data is received. Data is `JSON.parse`'d
+## Guides
 
-#### onOpen
+- [Shared clients](https://mehmetkose.github.io/react-websocket/guide/shared-clients) · [Messages and types](https://mehmetkose.github.io/react-websocket/guide/messages) · [Reconnecting and heartbeats](https://mehmetkose.github.io/react-websocket/guide/reconnecting)
+- [Suspense](https://mehmetkose.github.io/react-websocket/guide/suspense) · [Server rendering and Next.js](https://mehmetkose.github.io/react-websocket/guide/ssr) · [StrictMode, Activity and lifecycle](https://mehmetkose.github.io/react-websocket/guide/lifecycle)
+- [Authentication](https://mehmetkose.github.io/react-websocket/guide/authentication) · [Performance](https://mehmetkose.github.io/react-websocket/guide/performance) · [Testing](https://mehmetkose.github.io/react-websocket/guide/testing) · [Without React](https://mehmetkose.github.io/react-websocket/guide/without-react)
+- [Recipes](https://mehmetkose.github.io/react-websocket/recipes) · [Troubleshooting](https://mehmetkose.github.io/react-websocket/troubleshooting) · [Migrating from v2](https://mehmetkose.github.io/react-websocket/migration)
 
-The callback called when the connection is successfully opened.
+The docs source lives in [`docs/`](docs). Run `npm run docs:dev` to browse it locally.
 
-#### onClose
+## Compatibility
 
-The callback called when the connection is closed either due to server disconnect or network error.
+| | |
+| --- | --- |
+| React | 18 and 19 (`use(client.ready)` needs 19; `<Activity>` is handled on 19.2+). Tested in CI against both |
+| Runtimes | Modern browsers; Node via the `WebSocket` option |
+| Frameworks | Vite, Next.js (App and Pages Router), Remix/React Router, Astro islands, and any React setup |
 
-#### debug
+## Migrating from v2
 
-default: **false**
-Set to **true** to see console logging
+v2 was a `<Websocket>` class component. v3 replaces it with hooks: `<Websocket url onMessage />` becomes `useWebSocket(url, { onMessage })`, and `ref.sendMessage(msg)` becomes `send(msg)`. See the [migration guide](https://mehmetkose.github.io/react-websocket/migration) for the full mapping.
 
-#### reconnect
+## Example
 
-default: **true**
+[`example/`](example) has a Tornado broadcast server and a Vite + React 19 client.
 
-accelerated reconnection time
+## Contributing
 
+Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md). To report a vulnerability, follow [SECURITY.md](SECURITY.md).
 
 ## License
+
+[MIT](LICENSE)
+
 [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fmehmetkose%2Freact-websocket.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2Fmehmetkose%2Freact-websocket?ref=badge_large)