npm / typesense-fumadocs-adapter

typesense-fumadocs-adapter

What changed in typesense-fumadocs-adapter 0.4 to 0.5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.

1 deprecations4 new APIs and options5 behavior and defaults6 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

typesense-fumadocs-adapter 0.513 changes

Deprecates key in favor of cacheNamespace; key remains supported as an alias, and cacheNamespace takes precedence when both are supplied.
0.5.0release notes

Adds a hook option for configuring search caching.
0.5.0release notes
Adds a namespace to identify index revisions or custom search sources; namespaces augment the generated cache key.
0.5.0release notes
Adds configurable search caching with maxEntries and ttlMs.
0.5.0release notes
Adds an optional fourth AbortSignal argument so custom callbacks can forward cancellation to fetch or another transport.
0.5.0release notes

Obsolete Typesense requests are aborted when search parameters change or the hook unmounts.
0.5.0release notes
The default cache retains up to 100 responses.
0.5.0release notes
Setting either cache limit to zero disables caching.
0.5.0release notes
The default cache expiry is 5 minutes.
0.5.0release notes
Cache hits do not extend expiry, full caches evict the LRU entry, and expiry is checked on subsequent searches; displayed results do not refresh automatically.
0.5.0release notes

Prevents cached results from crossing locales, collections, clients, tags, or result formats.
0.5.0release notes
Preserves the internally debounced query when using a custom namespace.
0.5.0release notes
Prevents obsolete requests from overwriting current results, errors, loading state, or cached responses, including when callbacks ignore cancellation.
0.5.0release notes

Highlighted results now preserve markdown.
0.4.3release notes
The default Typesense tag field schema now uses the documented string type.
0.4.2release notes
Import errors now propagate, preventing failed syncs from updating the collection alias, deleting the previously working collection, or incorrectly reporting that syncing completed.
0.4.2release notes