ensure custom cache handlers are preloaded (#74622)
### What When specifying a custom "use cache" handler via `experimental.cacheHandlers`, the handler is not used during `next start` ### Why Custom cache handlers are initialized after the first request in `getIncrementalCache`. But because `unstable_preloadEntries` is the default during `next start`, we won't have loaded the custom cache handlers and the app will be stuck using the default cache handler once its set on the global namespace. ### How This updates `unstable_preloadEntries` to load any custom cache handlers so they're used instead of the default. Fixes #72552
Showing
14.7 KB