nestjs-redis
nestjs-redis copied to clipboard
refactor: update nestjs dependencies
PR Checklist
Please check if your PR fulfills the following requirements:
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)
PR Type
What kind of change does this PR introduce?
- [ ] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, local variables)
- [x] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Other... Please describe:
What is the current behavior?
Issue Number: #516
What is the new behavior?
Does this PR introduce a breaking change?
-
- [ ] Yes
-
- [x] No
Other information
Any estimate for merging this? My team is excited for SWC support in v10 Nest.js for which this bump is needed 🙏
Hey @liaoliaots ! Any updates?
@mahsumurebe, I think this PR should also update the requiremenets in the readme for Nest and Node
any news? it has been some time since last commit is this maintained? @liaoliaots
Hi @liaoliaots
Necessary improvements have been made. Can you check the pull request?
@liaoliaots Would much appreciate your support on this. We're kind of blocked on upgrading to Nest.js v10 because of the nestjs-redis not supporting it. Anything I can do from my side, I will be glad to support. I thank you for your efforts on this project.
Hi @liaoliaots
Can you check the pull request?
it's been close to 2 months now, is it time to create a fork instead?
it's been close to 2 months now, is it time to create a fork instead?
It's already created by @Songkeys
https://github.com/liaoliaots/nestjs-redis/issues/516#issuecomment-1626898431
It is possible to override dependencies in package.json
but do so at your own risk. The following worked via npm:
"overrides": {
"@liaoliaots/nestjs-redis": {
"@nestjs/common": "$@nestjs/common",
"@nestjs/core": "$@nestjs/core"
}
},