Local application publication
yarn atrium-starter publish and yarn atrium-showcase publish turn installed template packages into application-owned source files. They delegate to @agon/atrium-publisher. These are local initialization commands. Uploading the four packages to the GitLab registry is a separate maintainer release procedure.
Commands
After registry setup and installation, run the command from the initialized frontend directory:
yarn atrium-starter publishReplace atrium-starter with atrium-showcase for the complete demonstration template. Do not publish both into the same application directory.
| Option | Behavior |
|---|---|
--help. | Explain usage without writing or installing. |
publish --dry-run. | Validate the manifest and file destinations, then list changes without writing or installing. |
publish --no-install. | Write the application files and settings, leaving dependency installation to you. |
publish. | Write the application and run corepack yarn install. |
There is no overwrite or force option. Unknown arguments fail. Running the binary without arguments displays help.
File and manifest ownership
The template package declares an explicit application-source allowlist. Nested source directories and public assets are included. The publisher rejects traversal, source symlinks, symbolic destination paths, and incompatible file/directory types. It refuses differing application files instead of replacing them. Byte-identical files can be published again unchanged.
The current project’s package.json must exist and have an application name. Workspace roots and the template package itself are refused. Existing type, private, package-manager, engine, script, and dependency values must agree with required settings where they overlap. Matching Corepack integrity suffixes on the pinned Yarn declaration are retained. Unrelated settings are preserved.
The publisher adds @agon/atrium as a direct runtime dependency and installs the template’s pinned build dependencies. It preserves the installed starter/showcase dependency. It does not copy the template package’s name, version, bin, release metadata, or atriumTemplate declaration into the application manifest. It appends missing generated-file and environment-file patterns to .gitignore and leaves registry settings unchanged.
Dependency installation runs after file publication. If it fails, the command returns a nonzero status and leaves the materialized project available for repair with yarn install. Preflight catches known conflicts before writes. An unexpected filesystem failure during copying can leave a partial application. Review the error and retry after fixing the filesystem problem. There is no automatic rollback that could remove user files.
After initialization
The generated source is yours to customize. Publication is an initialization operation, not a migration tool. Running it after editing pages normally reports a conflict, which protects those edits.
You may keep the application-template package as a dependency, or remove it after initialization because the generated manifest directly declares the library and build dependencies:
yarn remove @agon/atrium-starterFor a showcase-derived application, remove @agon/atrium-showcase instead. This removes the local publication command and its transitive publisher when no other dependency needs them. Your generated application files remain in place. Rebuild and commit the manifest and lockfile changes.
Use deployment and upgrades to update the core library. If retaining the template package, update it to the matching release as well so it does not retain a second older Atrium dependency. Template source updates require an explicit comparison and application edit.
Author
Laurent Declercq l.declercq@agon-innovation.ch
License
Unless otherwise stated all source code is licensed under LGPL 2.1 and has the following copyright:
© 2026, Agon Partners Innovation AG, All rights reserved.The design material and the “Agon Ātrium” trademark is the property of their authors. Reuse of them without prior consent of their respective authors is strictly prohibited.
Version
Version: 20260921