You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If dynamic content were supported in production, perhaps the API should change, because useCache would be misleading, obviously implying that there's no caching at all.
The default behavior is to write the cache into the build directory with storage 'fs' driver (with 'cache:content' and 'cache:content:parsed' prefixes).
Alternatively the 'memory' driver could be used in development or production —simply decoupling from the filesystem.
Perhaps something like buildCache, optimizeCache, or staticCache would be more appropriate than useCache, or alternatively (to express the opposite) liveContent or dynamicContent.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe
Nuxt Content module v1 provided the
useCache
option to allow the prerendering/caching behavior to be disabled during production.This is highly desirable, if you want to provide dynamic content in production without rebuilding the application.
Describe the solution you'd like
Provide the
useCache
option in the configuration to determine caching behavior:Additional context
See discussion #2206
The text was updated successfully, but these errors were encountered: