TL;DR

Update the TypeScript JSDoc for cacheComponents to reflect that it opts into the runtime-first caching model, rather than automatically caching components.

Guidance

• Review the official Next.js documentation on cacheComponents to understand its actual behavior and intended use.
• Verify the current JSDoc text in editors to confirm the misleading description.
• Update the JSDoc comment to accurately describe the effect of enabling cacheComponents, using language consistent with the official documentation.
• Consider adding a note or example to the documentation to clarify the relationship between cacheComponents and use cache.

Example

// Example of updated JSDoc comment
/**
 * Enables the runtime-first caching model, excluding data fetching operations from pre-renders unless explicitly cached.
 * @see https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheComponents
 */

Notes

The fix relies on accurate documentation and understanding of the cacheComponents flag. Ensure that the updated JSDoc comment is consistent with the official Next.js documentation.

Recommendation

Apply workaround: Update the JSDoc comment to accurately reflect the behavior of cacheComponents, as this will help prevent confusion and ensure correct usage.