[sneridagh]

Adds @plone/registry/app-info, a virtual module like @plone/registry/blocks-docs and @plone/registry/plate-editor. Its default export is the name and version of the app (from its package.json) and of each of its add-ons, in add-on order:

import appInfo from '@plone/registry/app-info';
// { name: '@plone/aurora', version: '1.0.0-alpha.23', addons: [{ name: '@plone/cmsui', version: '…' }, …] }

• The Vite plugin writes .plone/registry.appInfo.js and aliases the import to it. It holds only names and versions, never file system paths, so client code can import it.
• virtual/app-info.js is the empty fallback for unit tests, Storybook and type checks, following virtual/README.md.
• The site overview reads the app version from it instead of importing apps/aurora/package.json from cmsui, which only worked inside this monorepo.

This is the base for #368: the installed add-ons list can be read from appInfo.addons instead of the addonsInfo export of the add-ons loader, which carries the absolute paths of the machine that built the app.

The addonsInfo export of the loader stays for now: apps/aurora/app/routes.ts (through registry.addonsInfo.json) and Volto still read it.

Tested: registry and SiteOverview unit tests, check:ts, and an Aurora build (the info lands only in the control panels chunk, with no local paths in the client bundle).

Assisted-by: Claude Opus 5.5

[read-the-docs-community]

Documentation build overview

📚 plone-registry | 🛠️ Build #35723427 | 📁 Comparing d24012c against latest (7e3cc8f)

  🔍 Preview build  

1 file changed

± conceptual-guides/add-on-loader.html