Standalone Angular 21 SSR app that consumes the published Uniform Angular packages from npm:
@uniformdev/context-angular@uniformdev/canvas-angular
cd examples/angular-starter
cp .env.example .env # fill UNIFORM_PROJECT_ID / UNIFORM_API_KEY / UNIFORM_PREVIEW_SECRET
npm install
npm start # http://localhost:4200Without credentials the app serves the bundled sample composition (offline mode).
npm run build
npm run serve:ssrnpm run manifest:pullIn Uniform project settings:
http://localhost:4200/api/preview?secret=<UNIFORM_PREVIEW_SECRET>
The floating product toolbar (@uniformdev/toolbar-angular) is mounted on the root
template as <uniform-toolbar simulator />. Context comes from provideUniformContext
in app.config.ts.
Until the packages are on npm, this starter depends on a local clone via file::
../../../toolbar/packages/toolbar
../../../toolbar/packages/toolbar-element
../../../toolbar/packages/toolbar-angular/dist
.npmrc sets install-links=true so those file: deps are copied instead of
symlinked — required to avoid a second @angular/core (NG0203) when Vite
follows the real path into the toolbar monorepo.
After publish, switch those deps to the published versions (for example ^20.73.0)
and you can drop install-links.
The footer app-context-toolbar strip is starter-only (launch signal / manifest reload)
and is separate from the product toolbar.
- Personalization and A/B testing are SSR'd (no prerender) so variants don't flash.
- The in-page Context inspector (
@uniformdev/context-angular-devtools) is not wired here yet — that package is not on npm. Use the Uniform Context Chrome extension (enableContextDevTools()is already enabled) or the product toolbar instead.