$ npm install redis
node-redis is a modern, high performance Redis client for Node.js.
Start a redis via docker:
docker run -p 6379:6379 -it redis/redis-stack-server:latest
To install node-redis, simply:
npm install redis
Looking for a high-level library to handle object mapping? See redis-om-node!
import { createClient } from 'redis';
const client = await createClient()
.on('error', err => console.log('Redis Client Error', err))
.connect();
await client.set('key', 'value');
const value = await client.get('key');
await client.close();
:warning: You MUST listen to
error
events. If a client doesn't have at least oneerror
listener registered and anerror
occurs, that error will be thrown and the Node.js process will exit. See theEventEmitter
docs for more details.
The above code connects to localhost on port 6379. To connect to a different host or port, use a connection string in the format redis[s]://[[username][:password]@][host][:port][/db-number]
:
createClient({
url: 'redis://alice:foobared@awesome.redis.server:6380'
});
You can also use discrete parameters, UNIX sockets, and even TLS to connect. Details can be found in the client configuration guide.
To check if the the client is connected and ready to send commands, use client.isReady
which returns a boolean. client.isOpen
is also available. This returns true
when the client's underlying socket is open, and false
when it isn't (for example when the client is still connecting or reconnecting after a network error).
There is built-in support for all of the out-of-the-box Redis commands. They are exposed using the raw Redis command names (HSET
, HGETALL
, etc.) and a friendlier camel-cased version (hSet
, hGetAll
, etc.):
// raw Redis commands
await client.HSET('key', 'field', 'value');
await client.HGETALL('key');
// friendly JavaScript commands
await client.hSet('key', 'field', 'value');
await client.hGetAll('key');
Modifiers to commands are specified using a JavaScript object:
await client.set('key', 'value', {
expiration: {
type: 'EX',
value: 10
},
condition: 'NX'
});
Replies will be mapped to useful data structures:
await client.hGetAll('key'); // { field1: 'value1', field2: 'value2' }
await client.hVals('key'); // ['value1', 'value2']
NOTE: you can change the default type mapping. See the Type Mapping documentation for more information.
If you want to run commands and/or use arguments that Node Redis doesn't know about (yet!) use .sendCommand()
:
await client.sendCommand(['SET', 'key', 'value', 'NX']); // 'OK'
await client.sendCommand(['HGETALL', 'key']); // ['key1', 'field1', 'key2', 'field2']
There are two functions that disconnect a client from the Redis server. In most scenarios you should use .close()
to ensure that pending commands are sent to Redis before closing a connection.
:warning: The
.quit()
and.disconnect()
methods have been deprecated in v5. For more details, refer to the v4-to-v5 guide.
.close()
const [ping, get] = await Promise.all([
client.ping(),
client.get('key'),
client.close()
]); // ['PONG', null]
try {
await client.get('key');
} catch (err) {
// ClientClosedError
}
:warning:
.close
is just like.quit()
which was depreacted in Redis 7.2. See the relevant section in the migration guide for more information.
.destroy()
Forcibly close a client's connection to Redis immediately. Calling destroy
will not send further pending commands to the Redis server, or wait for or parse outstanding responses.
Node Redis will automatically pipeline requests that are made during the same "tick".
client.set('Tm9kZSBSZWRpcw==', 'users:1');
client.sAdd('users:1:tokens', 'Tm9kZSBSZWRpcw==');
Of course, if you don't do something with your Promises you're certain to get unhandled Promise exceptions. To take advantage of auto-pipelining and handle your Promises, use Promise.all()
.
await Promise.all([
client.set('Tm9kZSBSZWRpcw==', 'users:1'),
client.sAdd('users:1:tokens', 'Tm9kZSBSZWRpcw==')
]);
The Node Redis client class is an Nodejs EventEmitter and it emits an event each time the network status changes:
Name | When | Listener arguments |
---|---|---|
connect |
Initiating a connection to the server | No arguments |
ready |
Client is ready to use | No arguments |
end |
Connection has been closed (via .quit() or .disconnect() ) |
No arguments |
error |
An error has occurred—usually a network issue such as "Socket closed unexpectedly" | (error: Error) |
reconnecting |
Client is trying to reconnect to the server | No arguments |
sharded-channel-moved |
See here | See here |
:warning: You MUST listen to
error
events. If a client doesn't have at least oneerror
listener registered and anerror
occurs, that error will be thrown and the Node.js process will exit. See theEventEmitter
docs for more details.
The client will not emit any other events beyond those listed above.
Node Redis is supported with the following versions of Redis:
Version | Supported |
---|---|
7.0.z | :heavy_check_mark: |
6.2.z | :heavy_check_mark: |
6.0.z | :heavy_check_mark: |
5.0.z | :heavy_check_mark: |
< 5.0 | :x: |
Node Redis should work with older versions of Redis, but it is not fully tested and we cannot offer support.
If you'd like to contribute, check out the contributing guide.
Thank you to all the people who already contributed to Node Redis!
This repository is licensed under the "MIT" license. See LICENSE.
© 2010 - cnpmjs.org x YWFE | Home | YWFE