New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any chance of updating Redis to v4 #78
Comments
@chris-elmstone Thank you for opening this issue.
Please provide an example to reproduce your conflicts. I believe you should not have any issue when using a different redis version than the one that this library is using (thanks to NPM dependency resolution algorithm). Here I am using redis@4.0.4: {
"dependencies": {
"redis": "^4.0.4",
"redis-smq": "^6.2.6"
}
} No conflict errors are expected when running this code: import { Consumer } from 'redis-smq';
import { createClient } from 'redis';
const c = new Consumer();
c.run(() => {
const r = createClient();
r.connect().then(() => r.info()).then((i) => {
console.log(i);
});
}); |
Closing as resolved |
Good afternoon weyoss, I am having a go at trying to use redis v4 with redis-smq and there is a type conflict:
They appear to have changed the But redis-smq uses the older naming convention: |
@PhilHannent I have re-opened this issue as it seems that there is a conflict problem that does not always occur. Please provide a full working example to reproduce your issue. You can try to run code from my previous comment #78 (comment) |
Using {
"dependencies": {
"redis": "^4.0.4",
"redis-smq": "^6.2.6"
}
} I am not having any issue, including your listing:
|
The explanation is obvious. When a module is being used in different libraries, NPM handles this situation depending on the following cases:
|
Good morning weyoss! To clarify, having the two side by side isn't the issue. It is where we are attempting to have one configuration for both our redis usage and for redis-smq. Because there is a difference in how the redis versions structure their configuration, it seems like we cannot re-use the same structure. I'll create a small example. |
@PhilHannent I got your point! So the issue is about using the redis configuration of your application which is using redis@v4 for In such case, definitely you are going to have the issue that you mentioned before.
There is no more need to create an example. The issue has been clarified. Thank you. |
Before redis is upgraded to v4, the only solution is to use a separate redis configuration for Please follow #86 to stay tuned about upgrading to redis@v4 |
Closing as resolved. |
Hello
The latest version of Redis allows for Promises and is a much nicer way of working, at the moment we use Handi-Redis to bypass this as using Redis 4 conflicts with this package's Redis 3.*.
I will look forward to your reply
Best Regards
Chris
The text was updated successfully, but these errors were encountered: