[In progress] Next.js 16 support

[AyronK]

🚀 Next.js 16 Support

You can check out the current state of integration with Next16 using 3.0.0-next16-alpha.0 version. Keep in mind it's highly experimental and too early to use in any production environments.

Overview

Next.js 16 is approaching release. This issue tracks the adaptation process and serves as a central discussion point for Next.js 16 compatibility.

Timeline & Expectations

⚠️ Important: Do not expect this package to be stable sooner than 1-2 months after Next.js 16.0.0 is officially released.

Given the number of issues and undocumented changes that came with Next.js 15, we strongly recommend not upgrading to 16.0.0 immediately if your setup includes a Redis cache handler. Exercise caution and wait for the ecosystem to stabilize.

Project Status

This package is currently maintained primarily by @AyronK with occasional community contributions. While we may allocate additional company resources if necessary, stability will largely depend on community effort.

Please note: This is a free, MIT-licensed package with no official support guarantees.

🤝 Help Needed

As Next.js 16 introduces new features, we need community support to ensure comprehensive coverage and documentation.

How you can contribute:

• Add examples for new Next.js 16 features to examples/redis-minimal
• Test the package with beta/RC versions and report findings
• Document edge cases and undocumented behaviors
• Open PRs against the next16 branch
• Report bugs clearly marking next16 in the issue title

The examples/redis-minimal project is already configured for Next.js 16 and serves as our testing ground for new features.

Resources

• 📖 Next.js 16 Beta Announcement
  Official Next.js 16 beta announcement
• 🔧 Draft PR #109: Next 16 support
  Track implementation progress here
• 💻 examples/redis-minimal
  Testing ground for Next.js 16 features

Discussion

This issue is open for:

• Reporting compatibility issues with Next.js 16
• Discussing breaking changes that affect this package
• Sharing testing results from beta/RC versions
• Coordinating migration efforts

Please comment below with any findings or concerns regarding Next.js 16 compatibility.

[mrjasonroy]

I started to look at this and am seeing what I can do in the next few days. @AyronK - what do you think about pinning versions of this repo to nextjs versions? Since the work for 16 might not work with 15 for example? Then users can upgrade the cache handler when they upgrade nextjs?

Either that or having multiple NextJS version examples that can be tested with each release.

[AyronK]

Yes I think it makes sense to introduce a clear indication of which version supports next 15 and 16. From my experience I got from upgrading from 14 to 15 there might be changes that are incompatible or exclusive. I personally don't have time to look into the migration sooner than in 1-2 weeks, we're also missing quite a lot of examples in our minimal project. But seeing there is more interest coming we'll try allocating a bit more resources into this project.

[epubreader]

I have upgraded my project to nextjs 16, what should I do?

[AyronK]

@epubreader I’ve written a draft checklist of items we need to review and adjust to make the library compatible with Next 16. I haven’t had time to create a canary version for Next 16 yet, but I’ll try to do that next week. If anyone has time to help with the adjustment process, please take a look at the checklist in the draft PR and open PRs to the next16 branch.

[AyronK]

I started a prerelease 3.0.0-next16-alpha.0 where you can check out the current state of integration.