vercel__next.js/test/e2e/app-dir/app-custom-cache-handler-errors/next.config.js at codex/fallback-root-cache - vercel__next.js - GetSkill.work

skills/vercel__next.js

mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00

Files

T

Sebastian "Sebbie" Silbermann ce207309be [test] Add coverage for throwing custom "use cache" cache handler (#95984 )

This is relevant if the cache is in a broken state or the keys or
entries are not suitable (e.g. an entry that's to large to be stored).

Revealed several oddities:
1. cache handler have no no sources content (not too bad since that
means the codeframe points into the problem `use cache` function which
is usually the cause)
2. A throwing `set` is swallowed in dev
3. A throwing `get` is logged as a caught error and an unhandled
rejection. This is spammy.

2026-07-21 10:23:54 +02:00

12 lines

207 B

JavaScript

Raw Permalink Blame History

 /**
  * @type {import('next').NextConfig}
  */
 const nextConfig = {
   cacheComponents: true,
   cacheHandlers: {
     default: require.resolve('./throwing-cache-handler.js'),
   },
 }
 module.exports = nextConfig