Feat: adding support for redis 5

[wisdomstar94]

If run or build the next app after using redis v5, will see the following error message.

unhandledRejection: TypeError: (0 , import_redis.commandOptions) is not a function

There is no error in the redis v4 version, so there seems to have been some change when the redis package moved from v4 to v5.

I hope the @trieb.work/nextjs-turbo-redis-cache package works fine with redis package v5.

Finally, thank you for developing and releasing the @trieb.work/nextjs-turbo-redis-cache package.

[JannikZed]

@wisdomstar94 could you please give me some context, what version of which package are you referring to? We have it all tested with redis client v4 and that is the currently supported version. Any reason, why you need v5? There are some API changes and I think we don't support that for now. Will first need to find out, what has changed etc.

[wisdomstar94]

@JannikZed

Yes, I know that the 'nextjs-turbo-redis-cache' package supports redis client v4.

However, I uploaded an issue because I wanted to know if you have any plans to support redis client v5.

[jnm733]

Same error for me with Redis 5.5.6 client package version.

It would be great to obtain support for version 5.

[tilman]

I have renamed the issue so we can add this Feature request to our roadmap.

To better understand your current problem please explain why you want to use redis client package v5? Did you face any problems with v4? Do you need any features only supported by v5?

[tilman]

Usage of v5 would need us to rewrite all redis operations to use redis.client.withAbortSignal(...).get instead of redis.client.get({abortSignal}, ...)

[jnm733]

I have renamed the issue so we can add this Feature request to our roadmap.

To better understand your current problem please explain why you want to use redis client package v5? Did you face any problems with v4? Do you need any features only supported by v5?

In our case is just for maintain all our dependencies updated.