Redis.Cluster.get and .set Properties do not exist on type 'Cluster'
See original GitHub issueWhen trying to call get
or set
on a cluster using “@types/ioredis”: “^4.0.9” and typescript there is no definition for Cluster.set or .get:
as per docs it says you can do this: https://github.com/luin/ioredis#cluster
I assume the type files are incorrect in @types/ioredis, I can’t find an easy way to fix them. (would rather open issue here than in the behemoth that is the @types repo)
Issue Analytics
- State:
- Created 5 years ago
- Comments:9
Top Results From Across the Web
SET
GET -- Return the old string stored at key, or nil if key did not exist. An error is returned and SET aborted...
Read more >ioredis
There are 4694 other projects in the npm registry using ioredis. ... ioredis supports the node.js callback style redis.get("mykey", (err, ...
Read more >Redis Extension Reference Guide
Redis is an in-memory data store used as a database, cache, streaming engine, ... configure the client type to cluster and configure the...
Read more >Spring Data Redis
The best way to get acquainted with these solutions is to read their documentation and follow their examples. It usually does not take...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hahaha. I have spent hours reading, why the normal Redis methods are missing on the Cluster, I though, this maybe a limitation from
redis
itself. Finally landed here.So for anyone else. All the commands from the normal Redis client are fully supported by Redis cluster too, it’s just missing in types.
Good work stale bot. This is still broken and still and an issue. Is it possible to just publish the generated definitions instead of the global ones just being broken and out of date?