Support Next 15 - When?

[yuriyyakym]

Hey!

Is there a plan to release Next 15 support?
I see there is an open PR.

The code in the PR looks good, though not passing some tests.

We're using Next 15, so supporting rsc data was crucial for us.
For now I had to monkey-patch cacheHandler like this (inspired by the PR):

const { get: originalGet, set: originalSet } = redisHandler;

Object.assign(redisHandler, {
    async get(key, meta) {
        const cachedData = await originalGet(key, meta);

        if (cachedData?.value?.kind === 'APP_PAGE') {
            cachedData.value.rscData = Buffer.from(cachedData.value.rscData, 'base64');
        }

        if (cachedData?.value?.kind === 'ROUTE') {
            cachedData.value.body = Buffer.from(cachedData.value.body, 'base64');
        }

        return cachedData;
    },
    set(key, data) {
        return originalSet(key, {
            ...data,
            value: {
                ...data.value,
                rscData: data.value.rscData?.toString('base64'),
            },
        });
    },
});

It would be nice if you release the version with Next 15 support under some rc/beta tag.

[better-salmon]

Hey @yuriyyakym! Thank you for bringing up this topic. I appreciate your contribution and interest in adding support for Next.js 15.

I was waiting for the RC 1 of Next.js 15 to continue working on this pull request. I will check if the latest canary of the Next.js is passing tests.

Regarding your workaround, it's great that you've found one! @neshca/cache-handler was designed to be customizable, so it's a good practice to do so.

[ScreamZ]

RC is available yet, any news ?

[better-salmon]

The RC is still at 0. I'm monitoring the canary branch to stay updated and waiting for RC1.

[jakehopking]

I've been pulling my hair out thinking there was an issue with my code! So it's simply that there's no support for Next 15 yet. I'm running v15.0.0-canary.190.
@yuriyyakym Would you mind sharing your full example so I can see if it works for me too?

Thanks!

[yuriyyakym]

import { CacheHandler } from '@neshca/cache-handler';
import createRedisHandler from '@neshca/cache-handler/redis-stack';
import { createClient } from 'redis';

CacheHandler.onCreation(async () => {
    const client = createClient({ url: process.env.WEBSITE_CACHE_REDIS_URL });
    
    client.on('error', (err) => {
        console.error(err);
    });

    await client.connect();

    // create your redis handler
    const redisHandler = await createRedisHandler({
        client,
        timeoutMs: 5000,
        keyPrefix: process.env.WEBSITE_CACHE_REDIS_PREFIX ?? '',
    });

    // monkey-patch it with my suggestion
    const { get: originalGet, set: originalSet } = redisHandler;
    Object.assign(redisHandler, {
        async get(key, meta) {
            const cachedData = await originalGet(key, meta);

            if (cachedData?.value?.kind === 'APP_PAGE') {
                cachedData.value.rscData = Buffer.from(cachedData.value.rscData, 'base64');
            }

            if (cachedData?.value?.kind === 'ROUTE') {
                cachedData.value.body = Buffer.from(cachedData.value.body, 'base64');
            }

            return cachedData;
        },
        set(key, data) {
            return originalSet(key, {
                ...data,
                value: {
                    ...data.value,
                    rscData: data.value.rscData?.toString('base64'),
                },
            });
        },
    });

    return { handlers: [redisHandler] };    
});

export default CacheHandler;

[jakehopking]

Thank you so much for this @yuriyyakym!
Caching with redis now actually almost works... I no long get 500 errors and infinite page reloads!!! Your patch successfully revalidates my unstable_cache instances with revalidateTag.
It doesn't revalidate paths unfortunately, so I'm unable to use yet. Did you have have any success with that?

@better-salmon do you have any insights on why calling revalidatePath wouldn't invalidate the cache key here?

[jake-lantern]

The revalidatePath successfully creates a hash entry in redis:

But not much else happens as far as I can tell:
[CacheHandler] [method: revalidateTag] [tags: []] Started revalidating tag in parallel.

[jake-lantern]

@better-salmon RC1 has landed :) https://github.com/vercel/next.js/releases/tag/v15.0.0-rc.1

[ScreamZ]

Rc2

[jakehopking]

Next 15 is stable: https://github.com/vercel/next.js/releases/tag/v15.0.0

Looking forward to the update from @better-salmon 🙏

[better-salmon]

Hi everyone!

I’m currently working on supporting Next.js 15. It will take a bit of time, as there are many changes in Next.js, some of which are breaking. I aim to maintain backward compatibility as much as possible. I appreciate your patience during this process!

[jakehopking]

Thank you @better-salmon 🙏

[ScreamZ]

You could take inspiration from next-intl (and @amannn which is a really smart developer) and especially this amannn/next-intl#1383 which has migrated the whole API for NextJS 15

[better-salmon]

Just a quick update! Believe it or not, I somehow managed to catch Covid-19 in 2024. 😆

But I’m all better now and back to work! Made a new PR #846

[ScreamZ]

So it's Covid 24

[jinl0ng]

Are there any updates? I noticed there's a Next15 branch in the repository. Can we directly use this branch now to support Next.js 15? Thank you.

[jdpnielsen]

Echoing this. Let us know if we can help test things, @better-salmon

[studentIvan]

Please don't forget about us @better-salmon we pray for your health and next 15 support :)

[studentIvan]

For somebody who running this plugin under redis-strings and still getting 500 can be helpful #846 (comment)

[studentIvan]

Looks like this plugin is abandoned, anybody knows the good alternative?

[ScreamZ]

I don't think this is hard stuff to create a new driver, I'll work on it in the next year if NextJS team doesn't do something about it. The real hard stuff is the opaque naming for routes.