feat: update ioredis to v5, make it a devDependency of the cache packages #172
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.
Why
ioredis v5 ships with its own TypeScript declarations. The breaking changes from v4 to v5 affect the code that instantiates ioredis, not the code that uses it. As such, I believe that entity is still technically compatible with ioredis v4, but for the sake of keeping our test matrix smaller, this commit uses just ioredis v5 in tests and makes v5 a peer dependency of
entity-cache-adapter-redis
.Additionally ioredis was a dependency of
entity-cache-adapter-redis
. I changed it to a devDependency and changed the import toimport type
since the package is used only for type checking.ioredis v5.0.0 changelog: https://github.com/luin/ioredis/releases/tag/v5.0.0. Notably it drops support for Node 10 and for custom Promise libraries, neither of which we use.
Test Plan
Building all packages (yarn) and testing them (yarn test) with Lerna succeeds