v3.4.0

What's Changed

Nuxt 4 compatibility (compatibilityVersion: 4)

The module should now be working when using compatibilityVersion: 4.

#77

New path for multiCache.serverOptions

To be in sync with the new folder structure of Nuxt 4 the server options file now defaults to <serverDir>/multiCache.serverOptions.ts which defaults to ~/server/multiCache.serverOptions.ts. The module will still look for the file in the app folder, however this will be removed in the next major release.

#84

Various

• fix: call handleRawCacheData in purgeTags event handler in #82
• fix: max age of 0 should mean uncacheable in useCachedAsyncData in #83

Full Changelog: v3.3.3...v3.4.0

v3.3.3

This release contains a bigger change in how cached routes are served, however because the previous change was partially broken, it is now released as a minor version to fix it for existing 3.3.x installs.

What's Changed

• feature: move serving of cached route to event handler in #73
• fix: add return type to useCachedAsyncData (#68) in #72
• fix: add server plugin when any feature is enabled (#69) in #71
• fix: setting headers via routeRules on cached routes (#64) in #66

Full Changelog: v3.3.1...v3.3.3

v3.3.1

The 3.3.0 release introduced a more robust way to hook into the nitro event lifecycle to handle route caching. Unfortunately it also introduced a bug where API routes were cached as well, even if not requested, if the page that made the API request was marked as cacheable.

What's Changed

• fix: don't set cache context on event.context (#64) by @dulnan in #65

Full Changelog: v3.3.0...v3.3.1

v3.3.0

What's Changed

• feat: refactor to use nitro hooks (#56) by @dulnan in #57
• feat: implement useCachedAsyncData by @dulnan in #58
• feat: implement "stale if error" and "stale while revalidate" by @dulnan in #61

Full Changelog: v3.2.0...v3.3.0

v3.2.0

What's Changed

• Cache management endpoints are excluded from enabledForRequest() #49
• Fix server response is never served from cache when using the fs driver #47
• New alterCachedHeaders option method to alter which headers are cached in route cache #30
• fix serverOptions types exports by @Applelo in #41
• fix: add consola to deps by @hpawa in #35
• fix(Route Cache): Filters set cookie header from page cache by @unluckynelson in #31
• Update overview/configuration.md doc by @valajan in #48
• Fix broken typedef export by @bgondy in #45
• Fix typo by @bgondy in #46
• chore(deps): update deps by @jpsc in #38

New Contributors

• @Applelo made their first contribution in #41
• @hpawa made their first contribution in #35
• @unluckynelson made their first contribution in #31
• @valajan made their first contribution in #48
• @bgondy made their first contribution in #45
• @jpsc made their first contribution in #38

Full Changelog: v3.1.1...v3.2.0

3.1.1

• Fix client side fatal exception in RenderCacheable due to changes in logging behavior
• Deprecate import of defineMultiCacheOptions from 'nuxt-multi-cache', as it results in the entire module being inlined in the server build. Instead it should now be imported like this, which will only import the helper method without any dependencies:
  import { defineMultiCacheOptions } from 'nuxt-multi-cache/dist/runtime/serverOptions'

3.1.0

• Uses setItemRaw for component and route cache to prevent JSON stringify/parse on large strings, which should improve performance
• New debug option for detailed logging. Setting it to false now only logs error messages (no more info/debug messages)
• On all caches, when a maxAge is defined for the cache item, it is additionally passed to the TransactionOptions of setItemRaw as the ttl property which is supported by the redis driver

v2.0.0 for Nuxt 3

Complete rewrite to support Nuxt 3. Most of the usage has changed due to the breaking changes from Nuxt 3.

The v2 releases are not compatible with Nuxt 2.

Migration guide from V1 to V2: https://nuxt-multi-cache.dulnan.net/overview/migrating-from-v1