rematch-websocket
v1.1.6
Published
A redux middleware to handle websocket connections
Downloads
1
Readme
rematch-websocket
Forked from redux-websocket to accomodate Rematch. Original README as seen below (keywords modified to suit actual usage of this package):
rematch-websocket
is a Redux middleware for managing data over a WebSocket connection.
This middleware uses actions to interact with a WebSocket connection including connecting, disconnecting, sending messages, and receiving messages. All actions follow the Flux Standard Action model.
Features
- Written in TypeScript.
- Interact with a WebSocket connection by dispatching actions.
- Connect to multiple WebSocket streams by creating multiple middleware instances.
- Handle WebSocket events with Redux middleware, integrate with Saga, and use reducers to persist state.
- Automatically handle reconnection.
Installation
$ npm i rematch-websocket
Configuration
Configure your Redux store to use the middleware with applyMiddleware
. This package exports a function to create an instance of a middleware, which allows for configuration options, detailed below. Furthermore, you can create multiple instances of this middleware in order to connect to multiple WebSocket streams.
import { applyMiddleware, compose, createStore } from 'redux';
import reduxWebsocket from 'rematch-websocket';
import reducer from './store/reducer';
// Create the middleware instance.
const reduxWebsocketMiddleware = reduxWebsocket();
// Create the Redux store.
const store = createStore(
reducer,
applyMiddleware(websocketMiddleware)
);
You may also pass options to the reduxWebsocket
function.
Available options
interface Options {
// Defaults to 'REDUX_WEBSOCKET'. Use this option to set a custom action type
// prefix. This is useful when you're creating multiple instances of the
// middleware, and need to handle actions dispatched by each middleware instance separately.
prefix?: string,
// Defaults to 2000. Amount of time to wait between reconnection attempts.
reconnectInterval?: number,
// Defaults to false. If set to true, will attempt to reconnect when conn is closed without error event
// e.g. when server closes connection
reconnectOnClose?: boolean,
// Callback when the WebSocket connection is open. Useful for when you
// need a reference to the WebSocket instance.
onOpen?: (socket: WebSocket) => void,
}
Usage
rematch-websocket
will dispatch some actions automatically, based on what the internal WebSocket connection. Some actions will need to be dispatched by you.
User dispatched actions
These actions must be dispatched by you, however we do export action creator functions that can be used.
⚠️ If you have created your middleware with a
prefix
option, make sure you pass that prefix as the second argument to all of these action creators.
➡️ REDUX_WEBSOCKET/WEBSOCKET_CONNECT
Example:
import { connect } from 'rematch-websocket';
store.dispatch(connect('wss://my-server.com'));
// You can also provide protocols if needed.
// See: https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/WebSocket
//
// Note that this function only allows passing an array of protocols, even though
// the spec allows passing a string or an array of strings. This is to support
// the prefix argument, in the case that you've prefixed your action names.
store.dispatch(connect('wss://my-server.com', ['v1.stream.example.com']));
// ...other ways to call this function:
store.dispatch(connect('wss://my-server.com', ['v1.stream.example.com'], 'MY_PREFIX'));
store.dispatch(connect('wss://my-server.com', 'MY_PREFIX'));
Arguments:
url
(string
): WebSocket URL to connect to.- [
protocols
] (string[]
): Optional sub-protocols. - [
prefix
] (string
): Optional action type prefix.
➡️ REDUX_WEBSOCKET/WEBSOCKET_DISCONNECT
Example:
import { disconnect } from 'rematch-websocket';
store.dispatch(disconnect());
Arguments:
- [
prefix
] (string
): Optional action type prefix.
➡️ REDUX_WEBSOCKET/WEBSOCKET_SEND
Example:
import { send } from 'rematch-websocket';
store.dispatch(send({ my: 'message' }));
Arguments:
message
(any
): Any JSON serializable value. This will be stringified and sent over the connection. If the value passed is not serializable,JSON.stringify
will throw an error.- [
prefix
] (string
): Optional action type prefix.
Library dispatched actions
These actions are dispatched automatically by the middlware.
⬅️ REDUX_WEBSOCKET/OPEN
Dispatched when the WebSocket connection successfully opens, including after automatic reconnect.
Structure
{
type: 'REDUX_WEBSOCKET/OPEN',
meta: {
timestamp: string,
},
}
⬅️ REDUX_WEBSOCKET/CLOSED
Dispatched when the WebSocket connection successfully closes, both when you ask the middleware to close the connection, and when the connection drops.
Structure
{
type: 'REDUX_WEBSOCKET/CLOSED',
meta: {
timestamp: string,
},
}
⬅️ REDUX_WEBSOCKET/MESSAGE
Dispatched when the WebSocket connection receives a message. The payload includes a message
key, which is JSON, and an origin
key, which is the address of the connection from which the message was recieved.
Structure
{
type: 'REDUX_WEBSOCKET/MESSAGE',
meta: {
timestamp: string,
},
payload: {
message: string,
origin: string,
},
}
⬅️ REDUX_WEBSOCKET/BROKEN
Dispatched when the WebSocket connection is dropped. This action will always be dispatched after the CLOSED
action.
Structure
{
type: 'REDUX_WEBSOCKET/BROKEN',
meta: {
timestamp: string,
},
}
⬅️ REDUX_WEBSOCKET/BEGIN_RECONNECT
Dispatched when the middleware is starting the reconnection process.
Structure
{
type: 'REDUX_WEBSOCKET/BEGIN_RECONNECT',
meta: {
timestamp: string,
},
}
⬅️ REDUX_WEBSOCKET/RECONNECT_ATTEMPT
Dispatched every time the middleware attempts a reconnection. Includes a count
as part of the payload.
Structure
{
type: 'REDUX_WEBSOCKET/RECONNECT_ATTEMPT',
meta: {
timestamp: string,
},
payload: {
count: number,
},
}
⬅️ REDUX_WEBSOCKET/RECONNECTED
Dispatched when the middleware reconnects. This action is dispached right before an OPEN
action.
Structure
{
type: 'REDUX_WEBSOCKET/RECONNECTED',
meta: {
timestamp: string,
},
}
⬅️ REDUX_WEBSOCKET/ERROR
General purpose error action.
Structure
{
type: 'REDUX_WEBSOCKET/ERROR',
error: true,
meta: {
timestamp: string,
message: string,
name: string,
originalAction: Action | null,
},
payload: Error,
}