mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Zack TannerandGitHub
bf27e24aca
When configuring `cacheMaxMemorySize` to disable memory caching (typically used for setups to adjust production caching behavior, especially in multi-process self-hosted setups), this inadvertently also disabled dev HMR caches which are intended as a performance optimization. As a result of this, the dev console would be spammed with "Single item size exceeds maxsize". It's still possible to use this configuration to set a larger cache, but otherwise it will have a minimum set to the previous default. Fixes NAR-463 x-ref: https://github.com/vercel/next.js/pull/85153#issuecomment-3429636751
12 lines
188 B
JavaScript
12 lines
188 B
JavaScript
/**
|
|
* @type {import('next').NextConfig}
|
|
*/
|
|
const nextConfig = {
|
|
// cacheMaxMemorySize: 0,
|
|
experimental: {
|
|
// serverComponentsHmrCache: false,
|
|
},
|
|
}
|
|
|
|
module.exports = nextConfig
|