Skip to content

better-content 0.10.0

Choose a tag to compare

View all tags
@Invalid8 Invalid8 released this 19 Sep 18:15
v0.10.0
724b47e

The subtraction release before 1.0. Four things were reachable that should not have been. Breaking changes are free now and permanent after 1.0.

Removed

  • StorageAdapter, a third spelling of the storage seam, exported from core and server, referenced nowhere in the implementation and in no doc. Use ClientStorageAdapter (upload) and ServerStorageAdapter (sign).
  • dirtyKey from better-content/core. It returned "collection:id", the engine's internal dirty-set key, so exporting it froze that format. setPath and getPath are unaffected.
  • PageContext from better-content/react. The raw context object pinned the two-context design as API. Use usePageContext, useCmsItem or useCmsEngine. PageContextValue stays as a type and CmsAuthContext stays deliberately.
  • resetGoogleKeyCache from better-content/auth/google, a test hook whose own docstring said so. The JWKS cache is internal now and still honours Google's cache-control.

Changed

  • engines.node is now >=20. Node 18 left maintenance in April 2025.
  • The root entry still re-exports core, and the docs now say so rather than leaving a second spelling undocumented.

Migration

Was Now
StorageAdapter ClientStorageAdapter or ServerStorageAdapter
dirtyKey(collection, id) your own template string, if you need it
useContext(PageContext) usePageContext()
resetGoogleKeyCache() nothing; the cache expires on max-age

No behaviour changed, no signatures changed, nothing was added. Requires create-better-content@0.9.0 or newer to scaffold.

Assets 2
Loading