Skip to content

Commit 4e0c11f

Browse files
committed
Additional fixes
1 parent 6e5c59d commit 4e0c11f

File tree

6 files changed

+157
-206
lines changed

6 files changed

+157
-206
lines changed

README.md

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,23 @@ This package was initially built on top of [`@neshca/cache-handler`](https://www
88

99
### 1.x.x -> 2.x.x
1010

11+
Starting with 2.0.0 we require Next 15 and Redis 5.
12+
13+
Remove `redis` from your dependencies if you don't need anything other than `@redis/client`. Then install `@redis/client`.
14+
15+
Upgrade Next and Redis in your project to:
16+
```
17+
"next": ">=15.2.4",
18+
"@redis/client": ">= 5.1.1"
19+
```
20+
21+
OR if you need full `redis` package
22+
23+
```
24+
"next": ">=15.2.4",
25+
"redis": ">= 5.1.1"
26+
```
27+
1128
1.x.x
1229

1330
```
@@ -22,7 +39,7 @@ const { CacheHandler } = require("@fortedigital/nextjs-cache-handler");
2239
module.exports = CacheHandler;
2340
```
2441

25-
####
42+
`createBufferStringHandler` was built into `redis-strings` and does not need to be used with Next 15 anymore.
2643

2744
### 1.2.x -> ^1.3.x
2845

@@ -66,6 +83,8 @@ if (process.env.NEXT_RUNTIME === "nodejs") {
6683

6784
## Installation
6885

86+
If you come from Next 14 or below, ensure to flush Redis cache before you run the project with this library. Cache format between Next 15 and Next <14 are not compatible!
87+
6988
## Next 15 Support and migration from `@neshca/cache-handler`
7089

7190
As `@neshca/cache-handler` does not officially support Next 15+ yet, we try to keep up with Next and prepare more or less temporary workarounds. At some point we will either create a fork of `@neshca/cache-handler` to fully support Next 15 or it gets updated by the maintainers. As for now we're building a set of decorators/workarounds you can use to build cache solutions for Next 15. We might need to do a full-blown rework which will be marked with a proper major version upgrade.

0 commit comments

Comments
 (0)