Why it's showing that handler is not enabled?

[RishikeshDarandale]

I get following debug message when using redis cache, what could be wrong with configuration?

 NEXT_PRIVATE_DEBUG_CACHE=1 npm run start

> my-web-app@1.0.0-development start
> next start

  ▲ Next.js 14.2.3
  - Local:        http://localhost:3000

 ✓ Starting...
 ✓ Ready in 640ms
using custom cache handler @neshca/cache-handler is not configured yet

Here is my cache-handler.js

const { CacheHandler } = require('@neshca/cache-handler');
const createRedisHandler = require('@neshca/cache-handler/redis-stack').default;
const createLruHandler = require('@neshca/cache-handler/local-lru').default;
const { createClient } = require('redis');
const { PHASE_PRODUCTION_BUILD } = require('next/constants');

CacheHandler.onCreation(async () => {
  let client;

  try {
    // Create a Redis client.
    client = createClient({
      url: 'redis://localhost:6379',
    });

    // Redis won't work without error handling.
    client.on('error', () => {});
  } catch (error) {
    console.warn('Failed to create Redis client:', error);
  }

  if (client) {
    try {
      console.info('Connecting Redis client...');

      // Wait for the client to connect.
      // Caveat: This will block the server from starting until the client is connected.
      // And there is no timeout. Make your own timeout if needed.
      await client.connect();
      console.info('Redis client connected.');
    } catch (error) {
      console.warn('Failed to connect Redis client:', error);

      console.warn('Disconnecting the Redis client...');
      // Try to disconnect the client to stop it from reconnecting.
      client
        .disconnect()
        .then(() => {
          console.info('Redis client disconnected.');
        })
        .catch(() => {
          console.warn(
            'Failed to quit the Redis client after failing to connect.',
          );
        });
    }
  }

  /** @type {import("@neshca/cache-handler").Handler | null} */
  let handler;

  console.info('The redis client is ready: ', client?.isReady);
  if (client?.isReady) {
    // Create the `redis-stack` Handler if the client is available and connected.
    handler = await createRedisHandler({
      client,
      keyPrefix: 'prefix:',
      timeoutMs: 1000,
    });
  } else {
    // Fallback to LRU handler if Redis client is not available.
    // The application will still work, but the cache will be in memory only and not shared.
    handler = createLruHandler();
    console.warn(
      'Falling back to LRU handler because Redis client is not available.',
    );
  }

  return {
    handlers: [handler],
  };
});

module.exports = CacheHandler;

and I have added following configuration in next.js

  cacheHandler:
    process.env.NODE_ENV === 'production'
      ? require.resolve('./cache-handler.js')
      : undefined,

[RishikeshDarandale]

@better-salmon , Can you please help me?

[RishikeshDarandale]

This is what I observed in the same application,

• the FETCH requests are not getting cached in REDIS when the dynamic pages are requested
  • FETCH is done by apollo graphql client( but they do cache in build/cache/fetch-cache in case npm start dev)
• the static page is getting cached in redis
  • the JSON is cached