Skip to content

Release 5.6.9

Choose a tag to compare

View all tags
@thet thet released this 25 Aug 22:18
· 55 commits to master since this release
5.6.9
8fdcc40

5.6.9 (2026-08-25)

Features

  • pat-contentbrowser: Initialize patterns on selected items. (8b94389)

    Do a registry scan on the selected items template, so that
    customizations can use Patterns in their SelectedItems.svelte templates.

Bug Fixes

  • bundle: share the Svelte runtime with module federation remotes (2cd08c5)

    Svelte keeps its reactivity state (effect tree etc.) in module-level
    variables, so the host bundle and remote (add-on) bundles must use the
    very same runtime instance. Without sharing, a Svelte component
    registered by an add-on bundle (e.g. via @plone/registry for
    pat-contentbrowser's componentRegistryKeys) is compiled against the
    add-on's own runtime copy and crashes in the host's mount() with
    "TypeError: Cannot read properties of null (reading 'nodes')".

  • Move svelte from devDependencies to dependencies — it is a runtime
    dependency and this way it becomes part of the generated module
    federation shared dependencies (also for add-ons which spread
    Mockup's dependencies into their shared config).
  • Add an explicit "svelte" shared entry (singleton) and a "svelte/"
    prefix share which covers deep imports like "svelte/internal/client"
    used by compiled Svelte 5 components — an exact-match entry does not
    cover those.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

Maintenance

  • pat contentbrowser: fix custom component documentation (3f73bcb)

    The option to use custom components from the @plone/registry component
    registry is named componentRegistryKeys with sub-key "selectedItem" —
    the README documented the outdated name customComponentKeys with
    sub-key "SelectedItem". Also fix the trailing commas in the JSON
    example (the pattern's JSON option parser would reject them), document
    the default component fallback and add a module federation shared
    config example for add-on bundles which register a custom Svelte
    component.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

  • pat contentbrowser: replace svelte-scrollto with native smooth scrolling (4f60a42)

    svelte-scrollto is unmaintained (last release 2019) and built for
    Svelte 3 — under pnpm it pulls in its own nested svelte@3 copy. With
    the Svelte runtime now shared via module federation ("svelte/" prefix
    share), those Svelte 3 modules (svelte/easing, svelte/internal) were
    provided unversioned into the share scope and caused build warnings.

The single usage — smoothly scrolling the miller columns to the right
— is covered by the native Element.scrollTo() with behavior "smooth",
which is supported by all targeted browsers.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

Assets 3
Loading