![Deno 2.2 Improves Dependency Management and Expands Node.js Compatibility](https://cdn.sanity.io/images/cgdhsj6q/production/97774ea8c88cc8f4bed2766c31994ebc38116948-1664x1366.png?w=400&fit=max&auto=format)
Security News
Deno 2.2 Improves Dependency Management and Expands Node.js Compatibility
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
socket.io-redis
Advanced tools
[![Build Status](https://travis-ci.org/socketio/socket.io-redis.svg?branch=master)](https://travis-ci.org/socketio/socket.io-redis) [![NPM version](https://badge.fury.io/js/socket.io-redis.svg)](http://badge.fury.io/js/socket.io-redis)
var io = require('socket.io')(3000);
var redis = require('socket.io-redis');
io.adapter(redis({ host: 'localhost', port: 6379 }));
By running socket.io with the socket.io-redis
adapter you can run
multiple socket.io instances in different processes or servers that can
all broadcast and emit events to and from each other.
If you need to emit events to socket.io instances from a non-socket.io process, you should use socket.io-emitter.
uri
is a string like localhost:6379
where your redis server
is located. For a list of options see below.
The following options are allowed:
key
: the name of the key to pub/sub events on as prefix (socket.io
)host
: host to connect to redis on (localhost
)port
: port to connect to redis on (6379
)subEvent
: optional, the redis client event name to subscribe to (message
)pubClient
: optional, the redis client to publish events onsubClient
: optional, the redis client to subscribe to events onrequestsTimeout
: optional, after this timeout the adapter will stop waiting from responses to request (1000ms
)withChannelMultiplexing
: optional, whether channel multiplexing is enabled (a new subscription will be trigggered for each room) (true
)If you decide to supply pubClient
and subClient
, make sure you use
node_redis as a client or one
with an equivalent API.
If you supply clients, make sure you initialized them with
the return_buffers
option set to true
.
You can supply ioredis as a client
by providing messageBuffer
as the subEvent option.
The redis adapter instances expose the following properties
that a regular Adapter
does not
uid
prefix
pubClient
subClient
requestsTimeout
Returns the list of client IDs connected to rooms
across all nodes. See Namespace#clients(fn:Function)
Returns the list of rooms the client with the given ID has joined (even on another node).
Access the pubClient
and subClient
properties of the
Redis Adapter instance to subscribe to its error
event:
var redis = require('socket.io-redis');
var adapter = redis('localhost:6379');
adapter.pubClient.on('error', function(){});
adapter.subClient.on('error', function(){});
If you need to create a redisAdapter to a redis instance that has a password, use pub/sub options instead of passing a connection string.
var redis = require('redis').createClient;
var adapter = require('socket.io-redis');
var pub = redis(port, host, { auth_pass: "pwd" });
var sub = redis(port, host, { return_buffers: true, auth_pass: "pwd" });
io.adapter(adapter({ pubClient: pub, subClient: sub }));
Make sure the return_buffers
option is set to true
for the sub client.
The socket.io-redis
adapter broadcasts and receives messages on particularly named Redis channels. For global broadcasts the channel name is:
prefix + '#' + namespace + '#'
In broadcasting to a single room the channel name is:
prefix + '#' + namespace + '#' + room + '#'
prefix
: The base channel name. Default value is socket.io
. Changed by setting opts.key
in adapter(opts)
constructornamespace
: See https://github.com/socketio/socket.io#namespace.room
: Used if targeting a specific room.A number of other libraries adopt this protocol including:
MIT
FAQs
[![Build Status](https://github.com/socketio/socket.io-redis/workflows/CI/badge.svg?branch=master)](https://github.com/socketio/socket.io-redis/actions) [![NPM version](https://badge.fury.io/js/socket.io-redis.svg)](http://badge.fury.io/js/socket.io-redis
The npm package socket.io-redis receives a total of 84,944 weekly downloads. As such, socket.io-redis popularity was classified as popular.
We found that socket.io-redis demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.