umbraco-bundle

An Umbraco extension bundle groups multiple extension manifests under a single bundle alias using JavaScript or TypeScript re-exports. This generates a bundle implementation and an umbraco-package.json entry that exports the required manifest objects.

An Umbraco extension bundle groups multiple backoffice extension manifests under a shared alias. You need one when packaging several extensions together, requiring an umbraco-package.json entry and a JavaScript or TypeScript file that re-exports the individual manifest objects.

Generating an umbraco-package.json manifest involves fetching the latest Umbraco extension-registry documentation, deciding which extensions to include, and outputting a correct bundle entry that exports extension manifests with valid type, name, alias, and element properties.

Yes, you can implement Umbraco backoffice extension bundles using TypeScript. The bundle implementation re-exports extension manifests from TypeScript files, ensuring the manifest objects contain valid type, name, alias, element, and optional conditions or meta properties.

An Umbraco extension manifest requires valid type, name, alias, and element fields. Optional conditions and meta properties can also be included to control visibility and provide additional metadata for the backoffice extension bundle implementation.

Yes, generating Umbraco bundle code requires fetching and following the official Umbraco Bundle and extension-registry documentation. This ensures the generated bundle and manifest structure, including the umbraco-package.json entry, matches current Umbraco guidance.