Repository navigation
docs(caching): add error event listener example for keyv redis store - #3683
Merged
kamilmysliwiec merged 2 commits intoOct 31, 2026
Merged
kamilmysliwiec merged 2 commits into
kamilmysliwiec merged 2 commits into
Conversation
Keep createKeyv() and its error listener in useFactory, and explain in a warning that Keyv throws on an unhandled 'error' event.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the alternative cache stores example using
@keyv/redis, connection drops or network partitions cause Keyv's internal Redis client to emit an'error'event. Without an explicit error listener, Node.js treats this as an unhandled EventEmitter error.This PR updates the multi-store
registerAsyncsnippet to show assigning the store instance and attaching an'error'listener, aligning with Keyv and Redis best practices.