Cheat Sheet

Bundler note: These examples import '.html' files as raw strings (showing '?raw' for Vite/esbuild). Configure your bundler as described in Importing external HTML templates with bundlers so the imports resolve to strings on Webpack, Parcel, etc.

Cheat Sheet

A quick reference for different aspects of Aurelia with minimal explanation.

Migration quick reference

Concern

Aurelia 1 idiom

Aurelia 2 equivalent

Notes

Bootstrapping

aurelia.use.standardConfiguration().feature(...).start().then(() => aurelia.setRoot())

Aurelia.register(...).app(AppRoot).start()

The aurelia package already registers StandardConfiguration plus a BrowserPlatform-backed IPlatform. Call app() with a component type or { host, component }.

Router

<router-view> + configureRouter

<au-viewport> + static routes/@route + RouterConfiguration

Router resources (viewport element, load/href attributes) live in @aurelia/router. Route lifecycle hooks are instance methods (canLoad, loading, canUnload, unloading).

Compose

<compose view-model="'./path'" ...>

<au-compose component.bind="ImportedType" template.bind="htmlString">

String-based module IDs and PLATFORM.moduleName are gone. Import classes directly or use () => import('./module') factories.

Task queue

TaskQueue from aurelia-task-queue

queueTask + queueAsyncTask + queueRecurringTask + runTasks

runTasks also runs recurring tasks, but wont stop it from running in the next interval

Compatibility gap

aurelia.use.plugin('@aurelia/compat-v1')

Aurelia.register(compatRegistration)

@aurelia/compat-v1 turns on delegate/call, .call bindings, BindingEngine, inlineView, and compose aliases so AU1 templates run while you migrate.

Bootstrapping

Simple

src/main.ts

import { Aurelia } from 'aurelia';
import { AppRoot } from './app-root';

const app = new Aurelia();
await app.app({
  component: AppRoot,
  host: document.querySelector('app-root'),
}).start();

Script tag (Vanilla JS)

Note: you can copy-paste the markup below into an html file and open it directly in the browser. There is no need for any tooling for this example.

index.html

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8" />
  <title>Aurelia 2 Script Example</title>
  
  <!-- Performance optimizations -->
  <link rel="dns-prefetch" href="//cdn.jsdelivr.net">
  <link rel="preconnect" href="https://cdn.jsdelivr.net" crossorigin>
  <link rel="modulepreload" href="https://cdn.jsdelivr.net/npm/aurelia@latest/+esm" crossorigin fetchpriority="high">
</head>
<body>
  <app-root></app-root>

  <script type="module">
    import { Aurelia, CustomElement } from 'https://cdn.jsdelivr.net/npm/aurelia@latest/+esm';

    const AppRoot = CustomElement.define({
      name: 'app-root',
      template: '${message}',
    }, class {
      message = 'Hello world!';
    });

    new Aurelia().app({ component: AppRoot, host: document.querySelector('app-root') }).start();
  </script>
</body>
</html>

Script tag (Vanilla JS - enhance)

Note: you can copy-paste the markup below into an html file and open it directly in the browser. There is no need for any tooling for this example.

index.html

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8" />
  <title>${title}</title>
  
  <!-- Performance optimizations -->
  <link rel="dns-prefetch" href="//cdn.jsdelivr.net">
  <link rel="preconnect" href="https://cdn.jsdelivr.net" crossorigin>
  <link rel="modulepreload" href="https://cdn.jsdelivr.net/npm/aurelia@latest/+esm" crossorigin fetchpriority="high">
</head>
<body>
  ${message}
  <script type="module">
    import { Aurelia } from 'https://cdn.jsdelivr.net/npm/aurelia@latest/+esm';

    const aurelia = new Aurelia();
    await aurelia.enhance({ component: { message: 'Hello world!' }, host: document.body }).start();
    await aurelia.enhance({ component: { title: 'Aurelia' }, host: document.head }).start();
  </script>
</body>
</html>

Multi-root

Note: the sample below mainly demonstrates stopping an existing instance of Aurelia and starting a new one with a different root and host. Do not consider this a complete example of a proper way to separate a private app root from public view, which is a topic of its own.

src/main.ts

import { Aurelia } from 'aurelia';
import { LoginWall } from './login-wall';

const app = new Aurelia();
await app.app({
  component: LoginWall,
  host: document.querySelector('login-wall'),
}).start();

src/login-wall.ts

import { Aurelia } from 'aurelia';
import { AppRoot } from './app-root';

export class LoginWall {
  constructor(private aurelia: Aurelia) {}

  async login() {
    await this.aurelia.stop();

    const newApp = new Aurelia();
    await newApp.app({
      component: AppRoot,
      host: document.querySelector('app-root'),
    }).start();
  }
}

Advanced (low-level)

When you need more control over the wireup and/or want to override some of the defaults wrapped by the 'aurelia' package and/or maximize tree-shaking of unused parts of the framework:

import { DI, Registration } from '@aurelia/kernel';
import {
  Aurelia,
  IPlatform,

  ITemplateCompilerRegistration,
  INodeObserverLocatorRegistration,

  DebounceBindingBehaviorRegistration,
  OneTimeBindingBehaviorRegistration,
  IfRegistration,
  ElseRegistration,
  RepeatRegistration,

  RefAttributePatternRegistration,
  DotSeparatedAttributePatternRegistration,

  DefaultBindingCommandRegistration,
  OneTimeBindingCommandRegistration,
  FromViewBindingCommandRegistration,
  ToViewBindingCommandRegistration,
  TwoWayBindingCommandRegistration,
  ForBindingCommandRegistration,
  TriggerBindingCommandRegistration,

  PropertyBindingRenderer,
  IteratorBindingRenderer,
  RefBindingRenderer,
  CustomElementRenderer,
  TemplateControllerRenderer,
  ListenerBindingRenderer,
  TextBindingRenderer,
} from '@aurelia/runtime-html';
import { BrowserPlatform } from '@aurelia/platform-browser';
import { AppRoot } from './app-root';

const container = DI.createContainer();
container.register(
  Registration.instance(IPlatform, BrowserPlatform.getOrCreate(globalThis)),

  // Default framework components
  ITemplateCompilerRegistration,
  INodeObserverLocatorRegistration,

  // Commonly used framework resources (only a small selection)
  DebounceBindingBehaviorRegistration, // &debounce
  OneTimeBindingBehaviorRegistration, // &oneTime
  IfRegistration, // if (if.bind)
  ElseRegistration, // else
  RepeatRegistration, // repeat (repeat.for)

  // Aurelia binding syntax
  RefAttributePatternRegistration, // ref
  DotSeparatedAttributePatternRegistration, // target.command (e.g. value.two-way, if.bind)

  // Commonly used Aurelia binding commands (only a small selection)
  DefaultBindingCommandRegistration, // .bind
  OneTimeBindingCommandRegistration, // .one-time
  FromViewBindingCommandRegistration, // .from-view
  ToViewBindingCommandRegistration, // .to-view
  TwoWayBindingCommandRegistration, // .two-way
  ForBindingCommandRegistration, // .for
  TriggerBindingCommandRegistration, // .trigger

  // Commonly used Aurelia renderers (only a small selection)
  PropertyBindingRenderer, // .bind, .one-time, .to-view, .from-view, .two-way bindings
  IteratorBindingRenderer, // .for bindings
  RefBindingRenderer, // ref bindings
  CustomElementRenderer, // custom element hydration
  TemplateControllerRenderer, // template controller hydration (if, repeat)
  ListenerBindingRenderer, // .trigger, .capture bindings
  TextBindingRenderer, // ${} text bindings
);

await new Aurelia(container).app({
  component: AppRoot,
  host: document.querySelector('app-root'),
}).start();

AppTask lifecycle hooks and deterministic teardown

import { Aurelia, AppTask, IWindow, runTasks } from 'aurelia';
import { IRouter, RouterConfiguration } from '@aurelia/router';

const au = new Aurelia();

await au
  .register(
    RouterConfiguration.customize({ historyStrategy: 'push', useUrlFragmentHash: false, activeClass: 'is-active' }),
    AppTask.creating(IWindow, (win) => {
      win.console.debug('App booting at', win.location.href);
    }),
    AppTask.activated(IRouter, (router) => router.load('home')),
  )
  .app({ host: document.querySelector('app-root')!, component: AppRoot })
  .start();

await tasksSettled();
await au.stop(true);

AppTask is implemented in packages/runtime-html/src/app-task.ts and exposes the same lifecycle slots that RouterConfiguration uses internally. tasksSettled waits for all tasks to be run first, so tests can flush work deterministically.

compat-v1 bridge while migrating

import { Aurelia } from 'aurelia';
import { compatRegistration, BindingEngine, computedFrom, inlineView } from '@aurelia/compat-v1';

Aurelia
  .register(compatRegistration)
  .app(AppRoot)
  .start();

export class LegacyPanel {
  static inject = [BindingEngine];

  constructor(private readonly engine: BindingEngine) {}

  @computedFrom('items.length')
  get count() {
    return this.items.length;
  }
}

@inlineView('<div>\n  <compose view-model.bind="childPath" model.bind="params"></compose>\n</div>')
export class LegacyShell {}

The compatRegistration bundle turns on the .call binding command, delegate syntax, BindingEngine, inlineView, and compose aliases so legacy Aurelia 1 templates keep rendering while you port them to native Aurelia 2 patterns.

Custom elements

With conventions

import { bindable, resolve } from 'aurelia';
import { IHttpClient } from '@aurelia/fetch-client';
export class ProductDetailCustomElement {
  static dependencies = [ImageViewerCustomElement, CurrencyValueConverter];
  static containerless = true;
  @bindable product: Product;
  readonly http: IHttpClient = resolve(IHttpClient);
}

Without conventions

import { customElement, bindable, resolve } from 'aurelia';
import { IHttpClient } from '@aurelia/fetch-client';
import template from './product-detail.html?raw';
@customElement({
  name: 'product-detail',
  template,
  dependencies: [ImageViewerCustomElement, CurrencyValueConverter],
  shadowOptions: { mode: 'open' },
})
export class ProductDetail {
  @bindable product: Product;
  readonly http: IHttpClient = resolve(IHttpClient);
}

Vanilla JS

import { CustomElement } from 'aurelia';
import { IHttpClient } from '@aurelia/fetch-client';
export const ProductDetail = CustomElement.define({
  name: 'product-detail',
  template: '<div>...</div>',
  dependencies: [ImageViewerCustomElement, CurrencyValueConverter],
  shadowOptions: { mode: 'open' },
  bindables: ['product'],
}, class {
  static inject = [IHttpClient];
  constructor(http) { this.http = http; }
});

Custom attributes

With conventions

import { bindable } from 'aurelia';
export class RippleCustomAttribute {
  @bindable color: string;
}

Without conventions

import { bindable, customAttribute } from 'aurelia';
@customAttribute('ripple')
export class Ripple {
  @bindable color: string;
}

Vanilla JS

import { CustomAttribute } from 'aurelia';
export const Ripple = CustomAttribute.define({
  name: 'ripple',
  bindables: ['color'],
}, class {

});

Template controllers

With conventions

import { IViewFactory, IRenderLocation, ISyntheticView, resolve } from 'aurelia';
export class NoopTemplateController {
  view: ISyntheticView = resolve(IViewFactory)
    .create()
    .setLocation(resolve(IRenderLocation));
}

Without conventions

import { templateController, IViewFactory, IRenderLocation, ISyntheticView, resolve } from 'aurelia';
@templateController('noop')
export class Noop {
  view: ISyntheticView = resolve(IViewFactory)
    .create()
    .setLocation(resolve(IRenderLocation));
}

Vanilla JS

import { CustomAttribute, IViewFactory, IRenderLocation } from 'aurelia';
export const Noop = CustomAttribute.define({
  name: 'noop',
  isTemplateController: true,
}, class {
  static inject = [IViewFactory, IRenderLocation];
  constructor(factory, location) {
    this.view = factory.create().setLocation(location);
  }
});

Binding behaviors

With conventions

import { ILogger, resolve } from 'aurelia';
export class LogBindingBehavior {
  constructor(
    readonly logger: ILogger = resolve(ILogger),
  ) {}
  bind(...args) {
    this.logger.debug('bind', ...args);
  }
  unbind(...args) {
    this.logger.debug('unbind', ...args);
  }
}

Without conventions

import { ILogger, bindingBehavior, resolve } from 'aurelia';
@bindingBehavior('log')
export class Log {
  constructor(
    readonly logger: ILogger = resolve(ILogger),
  ) {}
  bind(...args) {
    this.logger.debug('bind', ...args);
  }
  unbind(...args) {
    this.logger.debug('unbind', ...args);
  }
}

Vanilla JS

import { ILogger, BindingBehavior } from 'aurelia';
export const Log = BindingBehavior.define({
  name: 'log',
}, class {
  static inject = [ILogger];
  constructor(logger) { this.logger = logger; }
  bind(...args) {
    this.logger.debug('bind', ...args);
  }
  unbind(...args) {
    this.logger.debug('unbind', ...args);
  }
});

Value converters

With conventions

export class JsonValueConverter {
  toView(value) {
    return JSON.stringify(value);
  }
}

Without conventions

import { valueConverter } from 'aurelia';
@valueConverter('json')
export class Json {
  toView(value) {
    return JSON.stringify(value);
  }
}

Vanilla JS

import { ValueConverter } from 'aurelia';
export const Json = ValueConverter.define({
  name: 'json',
}, class {
  toView(value) {
    return JSON.stringify(value);
  }
});

Attribute patterns

import { attributePattern, AttrSyntax } from '@aurelia/template-compiler';

@attributePattern({ pattern: '[(PART)]', symbols: '[()]' })
export class BananaInBox {
  '[(PART)]'(rawName: string, rawValue: string, parts: readonly string[]): AttrSyntax {
    return new AttrSyntax(rawName, rawValue, parts[0], 'two-way');
  }
}

Binding commands / instruction renderer

CSS Classes & Styles

<!-- Dynamic classes -->
<div class="base-class" class.bind="dynamicClass">
<div class="nav-item" active.class="isActive">
<div class.bind="isSelected ? 'selected' : 'normal'">

<!-- Dynamic styles -->
<div style.bind="{ color: textColor, fontSize: size + 'px' }">
<div background-color.style="bgColor">
<div style.bind="`width: ${width}px; height: ${height}px`">

Observable Properties

import { observable } from '@aurelia/runtime';

export class MyComponent {
  @observable searchText = '';
  @observable selectedItem = null;

  // Automatically called when searchText changes
  searchTextChanged(newValue, oldValue) {
    this.filterItems(newValue);
  }

  // Automatically called when selectedItem changes  
  selectedItemChanged(newItem) {
    if (newItem) {
      this.onItemSelected(newItem);
    }
  }
}

Templating syntax

<!-- Render the 'firstName' and 'lastName' properties interpolated with some static text (reactive) -->
<div>Hello, ${firstName} ${lastName}</div>
<!-- Render the 'bgColor' property as a class name, interpolated with some static text (reactive) -->
<div class="col-md-4 bg-${bgColor}">

<!-- Bind the `someProp` property of the declaring component to the `prop` property of the declared component -->
<my-component prop.bind="someProp">
<!-- prop.bind is shorthand for prop.bind="prop" (when attr value is omitted, the left side of the dot is used as the value) -->
<my-component prop.bind>
<!-- This is another flavor of interpolation but in normal JS syntax, using .bind -->
<div class.bind="`col-md-4 bg-${bgColor}`">
<!-- Conditionally add the 'active' class using explicit class binding -->
<li class.bind="isActive ? 'active' : ''">
<!-- Conditionally add the 'active' class (the cleaner way) -->
<li active.class="isActive">
<!-- Bind to the 'style' attribute (the "old-fashioned" way) -->
<li style="background: ${bg}">
<!-- Bind to the 'style' attribute (the cleaner way) -->
<li background.style="bg">
<!-- Listen to the 'blur' event using a direct event listener on the element -->
<input blur.trigger="onBlur()">
<!-- Listen to the 'click' event using a event listener (only works with bubbling events) -->
<button click.trigger="onClick()">
<!-- Directly work with the event using the `$event` magic property -->
<form submit.trigger="$event.preventDefault()">
<!-- Set this html element to the 'nameInput' property on the declaring component -->
<input ref="nameInput">
<!-- Set the component instance of this <my-component> custom element
     to the 'myComponentViewModel' property on the declaring component -->
<my-component component.ref="myComponentViewModel">
<!-- Automatic two-way binding to an input (convention, equivalent to value.two-way) -->
<input value.bind="name">
<!-- Manual two-way binding to an input -->
<input value.to-view="name" change.trigger="handleNameChange($event.target.value)">

<!-- Debounce the notification when input value change for 200ms -->
<input value.bind="name & debounce">
<!-- Debounce the notification when input value change for 500ms -->
<input value.bind="name & debounce:500">
<!-- Throttle the notification when input value change for 200ms -->
<input value.bind="name & throttle">
<!-- Throttle the notification when input value change for 500ms -->
<input value.bind="name & throttle:500">

<!-- Render the 'message' property (non-reactive) -->
<div>${message & oneTime}</div>
<!-- Render the 'message' property (when the 'update' signal is sent manually) -->
<div>${message & signal:'update'}</div>
<!-- Render the 'timestamp' property formatted by the 'formatDate' ValueConverter -->
<div>${timestamp | formatDate}</div>

Built-in custom attributes & template controllers (AKA directives)

<!-- Conditionally render this nav-link (element is not created and will not exist in DOM if false) -->
<nav-link if.bind="isLoggedIn">
<!-- Conditionally display this nav-link (element is only hidden via CSS if false, and will always be created and exist in DOM) -->
<nav-link show.bind="isLoggedIn">
<!-- Conditionally hide this nav-link (element is only hidden via CSS if true, and will always be created and exist in DOM) -->
<nav-link hide.bind="isAnonymous">
<!-- Conditionally render one thing or the other -->
<p if.bind="product.stockQty > 0">${product.stockQty}</p>
<p else>Out of stock!</p>
<!-- Conditionally render one or more out of several things based on a condition -->
<template switch.bind="status">
  <span case="received">Order received.</span>
  <span case="dispatched">On the way.</span>
  <span case="processing">Processing your order.</span>
  <span case="delivered">Delivered.</span>
</template>
<!-- Render a list of items -->
<div repeat.for="item of items">${item}</div>
<!-- Render something on a different location in the DOM -->
<modal-dialog portal="app-root">
<!-- Create a slot for content projection -->
<my-component>
  <div au-slot="header">Header content</div>
  <div au-slot="footer">Footer content</div>
  <div au-slot>Default slot content</div>
</my-component>
<!-- Create a new binding scope with a specific object -->
<div with.bind="user">
  <p>${firstName} ${lastName}</p>
  <p>${email}</p>
</div>

Lifecycle hooks

Migrating from v1

Rename bind to binding
- If you had timing issues in bind and used the queueMicroTask to add some delay (or used attached for things that really should be in bind), you could try using bound instead (and remove the queueMicroTask). This hook was added to address some edge cases where you need information that's not yet available in bind, such as from-view bindings and refs.
- If you used CompositionTransaction in the bind hook to await async work, you can remove that and simply return a promise (or use async/await) in binding instead. The promise will be awaited by the framework before rendering the component or binding and of its children.
Rename attached to attaching
- If you had timing issues in attached and used queueMicroTask or even queueTask to add some delay, you can probably remove the queueMicroTask / queueTask and keep your logic in the attached hook. Where attaching is the new "called as soon as this thing is added to the DOM", attached now runs much later than it did in v1 and guarantees that all child components have been attached as well.
Rename unbind to unbinding (there is no unbound)
Rename detached to detaching (there is no more detached)
- If you really need to run logic after the component is removed from the DOM, use unbinding instead.
If you need the owningView, consider the interface shown below: what was "view" in v1 is now called "controller", and what was called "owningView" in v1 is now called "parentController" (or simply parent in this case). You can inject it via DI using resolve(IController), therefore it's no longer passed-in as an argument to created.

The view model interfaces

You can import and implement these in your components as a type-checking aid, but this is optional.

interface ICustomElementViewModel {
  define(
    controller: IDryCustomElementController,
    parentContainer: IContainer,
    definition: CustomElementDefinition): PartialCustomElementDefinition | void
  hydrating(controller: IContextualCustomElementController): void;
  hydrated(controller: ICompiledCustomElementController): void;
  created(controller: ICustomElementController): void;

  binding(initiator: IHydratedController, parent: IHydratedController | null): void | Promise<void>;
  bound(initiator: IHydratedController, parent: IHydratedController | null): void | Promise<void>;
  attaching(initiator: IHydratedController, parent: IHydratedController | null): void | Promise<void>;
  attached(initiator: IHydratedController): void | Promise<void>;

  detaching(initiator: IHydratedController, parent: IHydratedController | null): void | Promise<void>;
  unbinding(initiator: IHydratedController, parent: IHydratedController | null): void | Promise<void>;

  dispose(): void;

  accept(visitor: ControllerVisitor): void | true;
}

interface ICustomAttributeViewModel {
  link(
    flags: LifecycleFlags,
    controller: IHydratableController,
    childController: ICustomAttributeController,
    target: INode,
    instruction: Instruction): void;
  created(controller: ICustomAttributeController): void;

  binding(initiator: IHydratedController, parent: IHydratedController): void | Promise<void>;
  bound(initiator: IHydratedController, parent: IHydratedController): void | Promise<void>;
  attaching(initiator: IHydratedController, parent: IHydratedController): void | Promise<void>;
  attached(initiator: IHydratedController): void | Promise<void>;

  detaching(initiator: IHydratedController, parent: IHydratedController): void | Promise<void>;
  unbinding(initiator: IHydratedController, parent: IHydratedController): void | Promise<void>;

  dispose(): void;

  accept(visitor: ControllerVisitor): void | true;
}

interface IRouteViewModel extends ICustomElementViewModel {
  canLoad(
    params: Params,
    next: RouteNode,
    current: RouteNode | null): boolean | NavigationInstruction | NavigationInstruction[] | Promise<boolean | NavigationInstruction | NavigationInstruction[]>;
  loading(
    params: Params,
    next: RouteNode,
    current: RouteNode | null): void | Promise<void>;
  canUnload(
    next: RouteNode | null,
    current: RouteNode): boolean | Promise<boolean>;
  unload(
    next: RouteNode | null,
    current: RouteNode): void | Promise<void>;
}

Dependency Injection

Migrating from v1

Most stuff from v1 will still work as-is, but we do recommend that you consider using DI.createInterface liberally to create injection tokens, both within your app as well as when authoring plugins.

Consumers can use these as either parameter decorators or as direct values to .get(...) / static inject = [...].

The benefit of parameter decorators is that they also work in Vanilla JS with babel and will work natively in browsers (without any tooling) once they implement them.

They are, therefore, generally the more forward-compatible and consumer-friendly option.

Creating an interface

Note: this is a multi-purpose "injection token" that can be used as a plain value (also in VanillaJS) or as a parameter decorator (in TypeScript only)

Strongly-typed with default

Useful when you want the parameter decorator and don't need the interface itself.

export class ApiClient {
  async getProducts(filter) { /* ... */ }
}
export interface IApiClient extends ApiClient {}
export const IApiClient = DI.createInterface<IApiClient>('IApiClient', x => x.singleton(ApiClient));

No default (more loosely coupled)

export interface IApiClient {
  getProducts(filter): Promise<Product[]>;
}
export const IApiClient = DI.createInterface<IApiClient>('IApiClient');

// Needs to be explicitly registered with the container when no default is provided
container.register(Registration.singleton(IApiClient, ApiClient));

Injecting an interface

// Note: in the future there will be a convention where the decorator is no longer necessary with interfaces
export class MyComponent {
  private api: IApiClient = resolve(IApiClient);
}
// Once the convention is in place:
export class MyComponent {
  constructor(private api: IApiClient) {}
}

Registration types

Creating resolvers explicitly

This is more loosely coupled (keys can be declared independently of their implementations) but results in more boilerplate. More typical for plugins that want to allow effective tree-shaking, and less typical in apps.

These can be provided directly to e.g. au.register(dep1, dep2) as global dependencies (available in all components) or to the static dependencies = [dep1, dep1] of components as local dependencies.

Registration.singleton(key, SomeClass); // Single container-wide instance
Registration.transient(key, SomeClass); // New instance per injection
Registration.callback(key, (container) => /* some factory fn */); // Callback invoked each time
Registration.cachedCallback(key, (container) => /* some factory fn */); // Callback invoked only once and then cached
Registration.aliasTo(originalKey, aliasKey);
Registration.instance(key, someInstance);

Decorating classes

// Registers in the root container
@singleton
export class SomeClass {}

// Registers in the requesting container
@singleton({ scoped: true })
export class SomeClass {}

@transient
export class SomeClass {}

Customizing injection

export class MyLogger {
  // Resolve all dependencies associated with a key (zero to many)
  private sinks: ISink[] = resolve(all(ISink));
}

export class MyComponent {
  // Resolve a factory function that returns the dependency when called
  private getFoo: () => IFoo = resolve(lazy(IFoo));

  doStuff() {
    const foo = this.getFoo();
  }
}

export class MyComponent {
  // Use class properties with default values instead of constructor parameters
  private name: string = 'my-component';
}

export class MyComponent {
  // Yield undefined (instead of throwing) if no registration exists
  private foo: IFoo = resolve(optional(IFoo));
}

export class MyComponent {
  // Explicitly create a new instance, even if the key is already registered as a singleton
  private foo: IFoo = resolve(newInstanceOf(IFoo));
}

// Extend Window type for custom added properties or e.g. third party libraries like Redux DevTools which do so, yet inject the actual window object
export interface IReduxDevTools extends Window {
  devToolsExtension?: DevToolsExtension;
  __REDUX_DEVTOOLS_EXTENSION__?: DevToolsExtension;
}

export class MyComponent {
  // Note that the type itself is not responsible for resolving the proper key but the decorator
  private window: IReduxDevTools = resolve(IWindow);
}

Using lifecycle hooks in a non-blocking fashion but keeping things awaitable

Example that blocks rendering (but is simplest to develop)

<div>${data}</div>

export class MyComponent {
  async loading(params) {
    this.data = await loadData(params.id);
  }
}

Example that does not block rendering and avoids race conditions (without task queue)

<div if.bind="loadDataPromise">Loading...</div>
<div else>...</div>

export class MyComponent {
  loading(params) {
    this.loadDataPromise = loadData(params.id).then(data => {
      this.data = data;
      this.loadDataPromise = null;
    });
  }
  unload() {
    return this.loadDataPromise;
  }
}

Example that does not block rendering and avoids race conditions (with task queue)

<div if.bind="loadDataTask">Loading...</div>
<div else>...</div>

import { resolve } from '@aurelia/kernel';
import { queueAsyncTask, runTasks } from '@aurelia/runtime';
import { IPlatform } from '@aurelia/runtime-html';

export class MyComponent {
  private readonly platform = resolve(IPlatform);

  loading(params) {
    this.loadDataTask = queueAsyncTask(async () => {
      this.data = await loadData(params.id);
      this.loadDataTask = null;
    });
  }
}

Apply the practices above consistently, and you'll reap the benefits:

import { resolve } from '@aurelia/kernel';
import { tasksSettled } from '@aurelia/runtime';
import { IPlatform } from '@aurelia/runtime-html';

// Await all pending tasks (useful in unit, integration and e2e tests)
await tasksSettled();

Route Configuration

import { resolve } from '@aurelia/kernel';
import { IRouter, route } from '@aurelia/router';

@route({
  routes: [
    { path: '', component: () => import('./home'), title: 'Home' },
    { path: '/products/:id', component: () => import('./product-detail'), title: 'Product' },
    { path: '/about', component: () => import('./about'), title: 'About' },
  ]
})
export class AppRoot {
  constructor(private router: IRouter = resolve(IRouter)) {}
}

import { resolve } from '@aurelia/kernel';
import { IRouter, IRouteContext } from '@aurelia/router';

export class MyComponent {
  private readonly router = resolve(IRouter);
  private readonly routeContext = resolve(IRouteContext);

  // Navigate to a route
  goToProduct(id: string) {
    return this.router.load(`/products/${id}`);
  }

  // Navigate with parameters
  goToProductWithQuery(id: string) {
    return this.router.load(`/products/${id}`, { queryParams: { tab: 'reviews' } });
  }

  // Check if a route is active relative to this component's context
  isActive(path: string): boolean {
    return this.router.isActive(path, this.routeContext);
  }
}

IRouter.isActive always needs a RouteContextLike. Inside routed components you can resolve(IRouteContext) as shown above; elsewhere pass the owning element/controller or an explicit IRouteContext so the router knows which viewport tree to compare against.

Router Viewports

<!-- Default viewport -->
<au-viewport></au-viewport>

<!-- Named viewport -->
<au-viewport name="sidebar"></au-viewport>

<!-- Multiple viewports -->
<au-viewport name="main"></au-viewport>
<au-viewport name="aside"></au-viewport>

Router Links in Templates

<!-- load triggers router navigation and keeps <a> hrefs in sync automatically -->
<a load="products">Products</a>

<!-- Supply route params via params.bind (object or array) -->
<a load="products" params.bind="{ id: product.id }">View Product</a>

<!-- Highlight active routes by binding to the 'active' property provided by load -->
<a load="products" active.class="active">Products</a>

Configure RouterConfiguration.customize({ activeClass: 'active' }) to have the load custom attribute toggle that class automatically, or bind active.two-way/active.class as above for fine-grained control. Because load resolves the element's href internally, these links continue to work even without JavaScript and honor the app's base URL.

Validation

Basic Validation Rules

import { resolve } from '@aurelia/kernel';
import { IValidationRules } from '@aurelia/validation';

export class UserForm {
  name: string = '';
  email: string = '';
  age: number = 0;

  private readonly validationRules = resolve(IValidationRules);

  constructor() {
    this.validationRules
      .on(this)
      .ensure('name')
        .required()
        .minLength(2)
        .maxLength(50)
      .ensure('email')
        .required()
        .email()
      .ensure('age')
        .required()
        .min(18)
        .max(120);
  }
}

Validation Controller

import { newInstanceForScope, resolve } from '@aurelia/kernel';
import { IValidationController } from '@aurelia/validation-html';

export class UserForm {
  private readonly validationController = resolve(newInstanceForScope(IValidationController));

  async submit() {
    const result = await this.validationController.validate();
    if (result.valid) {
      // Submit form
    }
  }
}

Template Validation Display

<form>
  <input type="text" value.bind="name">
  <div class="error" repeat.for="error of validationController.errors">
    <span if.bind="error.propertyName === 'name'">${error.message}</span>
  </div>

  <button type="submit" click.trigger="submit()">Submit</button>
</form>

Animation

CSS Animations

import { AnimationEvent } from '@aurelia/runtime-html';

export class FadeInOut {
  enter(element: Element): void {
    element.classList.add('fade-in');
  }

  leave(element: Element): Promise<void> {
    return new Promise(resolve => {
      element.classList.add('fade-out');
      element.addEventListener('animationend', () => resolve(), { once: true });
    });
  }
}

Web Animations API

export class SlideAnimation {
  enter(element: Element): Animation {
    return element.animate([
      { transform: 'translateX(-100%)' },
      { transform: 'translateX(0)' }
    ], {
      duration: 300,
      easing: 'ease-out'
    });
  }

  leave(element: Element): Animation {
    return element.animate([
      { transform: 'translateX(0)' },
      { transform: 'translateX(100%)' }
    ], {
      duration: 300,
      easing: 'ease-in'
    });
  }
}

Router Transition Animations

@route({
  routes: [
    {
      path: '/page1',
      component: () => import('./page1'),
      transitionPlan: {
        enter: 'slide-in-right',
        leave: 'slide-out-left'
      }
    }
  ]
})
export class AppRoot {}

Programmatic Animations

export class MyComponent {
  async animateElement() {
    const element = document.querySelector('.my-element');
    await element.animate([
      { opacity: 0, transform: 'scale(0.5)' },
      { opacity: 1, transform: 'scale(1)' }
    ], { duration: 500 }).finished;
  }
}

UI Composition

au-compose

<!-- Compose with component -->
<au-compose component.bind="MyComponent" model.bind="data"></au-compose>

<!-- Compose with view-model -->
<au-compose view-model.bind="viewModel" model.bind="data"></au-compose>

<!-- Compose with template -->
<au-compose template.bind="htmlTemplate" model.bind="data"></au-compose>

Programmatic Composition

import { ICompositionRoot } from '@aurelia/runtime-html';

export class MyComponent {
  constructor(private compositionRoot: ICompositionRoot = resolve(ICompositionRoot)) {}

  async composeComponent() {
    const composition = await this.compositionRoot.compose({
      component: MyDynamicComponent,
      host: this.containerElement,
      model: { data: 'example' }
    });

    return composition;
  }
}

Synthetic Views

Creating Synthetic Views

import { IViewFactory, IRenderLocation, ISyntheticView } from '@aurelia/runtime-html';

export class MyComponent {
  constructor(
    private viewFactory: IViewFactory = resolve(IViewFactory),
    private renderLocation: IRenderLocation = resolve(IRenderLocation)
  ) {}

  createView(): ISyntheticView {
    const view = this.viewFactory
      .create()
      .setLocation(this.renderLocation);

    view.activate(this, null);
    return view;
  }
}

Template Controllers with Synthetic Views

import { templateController, IViewFactory, IRenderLocation } from '@aurelia/runtime-html';

@templateController('my-repeat')
export class MyRepeat {
  items: any[] = [];

  constructor(
    private viewFactory: IViewFactory = resolve(IViewFactory),
    private renderLocation: IRenderLocation = resolve(IRenderLocation)
  ) {}

  itemsChanged() {
    // Create views for each item
    this.items.forEach(item => {
      const view = this.viewFactory.create().setLocation(this.renderLocation);
      view.activate(item, null);
    });
  }
}

Shadow DOM & Slots

Shadow DOM Setup

@customElement({
  name: 'my-card',
  template: `
    <div class="card">
      <div class="header">
        <au-slot name="header">Default Header</au-slot>
      </div>
      <div class="content">
        <au-slot>Default Content</au-slot>
      </div>
    </div>
  `,
  shadowOptions: { mode: 'open' }
})
export class MyCard {}

Using Slots

<my-card>
  <div au-slot="header">
    <h2>Custom Header</h2>
  </div>
  <div au-slot>
    <p>Custom content goes here</p>
  </div>
</my-card>

Replaceable Parts

@customElement({
  name: 'data-table',
  template: `
    <table>
      <thead>
        <tr>
          <th repeat.for="column of columns">
            <au-slot name="header" model.bind="column">
              ${column.title}
            </au-slot>
          </th>
        </tr>
      </thead>
      <tbody>
        <tr repeat.for="row of rows">
          <td repeat.for="column of columns">
            <au-slot name="cell" model.bind="{ row, column }">
              ${row[column.key]}
            </au-slot>
          </td>
        </tr>
      </tbody>
    </table>
  `
})
export class DataTable {
  @bindable columns: Column[] = [];
  @bindable rows: any[] = [];
}

UI Virtualization

Virtual Repeat

<!-- Basic virtual repeat -->
<div virtual-repeat.for="item of items" style="height: 50px;">
  ${item.name}
</div>

<!-- Virtual repeat with custom item height -->
<div virtual-repeat.for="item of items" item-height="75">
  <div class="item">${item.name}</div>
</div>

Virtual Repeat Configuration

export class VirtualList {
  items: any[] = [];

  // Configure virtual repeat
  virtualRepeatConfig = {
    itemHeight: 60,
    bufferSize: 10,
    scrollingEnabled: true
  };
}

<div virtual-repeat.for="item of items"
     item-height.bind="virtualRepeatConfig.itemHeight"
     buffer-size.bind="virtualRepeatConfig.bufferSize">
  ${item.name}
</div>

Testing

Component Testing

import { TestContext } from '@aurelia/testing';
import { MyComponent } from './my-component';

describe('MyComponent', () => {
  it('should render correctly', async () => {
    const { startPromise, tearDown, component } = TestContext.create(
      '<my-component name.bind="name"></my-component>',
      MyComponent,
      { name: 'Test' }
    );

    await startPromise;

    expect(component.name).toBe('Test');

    await tearDown();
  });
});

Integration Testing

import { TestContext } from '@aurelia/testing';
import { IRouter, IRouteContext } from '@aurelia/router';
import { AppRoot } from './app-root';

describe('App Integration', () => {
  it('should navigate between routes', async () => {
    const { startPromise, tearDown, app } = TestContext.create(
      '<app-root></app-root>',
      AppRoot
    );

    await startPromise;

    // Test navigation
    const router = app.container.get(IRouter);
    const routeContext = app.container.get(IRouteContext);
    await router.load('/products');

    expect(router.isActive('/products', routeContext)).toBe(true);

    await tearDown();
  });
});

Internationalization (i18n)

Basic Setup

import { I18N } from '@aurelia/i18n';

export class MyComponent {
  constructor(private i18n: I18N = resolve(I18N)) {}

  created() {
    this.i18n.setLocale('en');
  }
}

Template Usage

<!-- Simple translation -->
<p>${'hello' | t}</p>

<!-- Translation with parameters -->
<p>${'welcome' | t: { name: user.name }}</p>

<!-- Translation with attributes -->
<input type="text" placeholder="${'enter_name' | t}">

<!-- Date/number formatting -->
<p>${date | df}</p>
<p>${amount | nf}</p>

Programmatic Usage

export class MyComponent {
  constructor(private i18n: I18N = resolve(I18N)) {}

  getTranslation() {
    const message = this.i18n.tr('hello');
    const parameterized = this.i18n.tr('welcome', { name: 'John' });
    return { message, parameterized };
  }

  changeLanguage(locale: string) {
    this.i18n.setLocale(locale);
  }
}

State Management

Observable State

import { observable } from '@aurelia/runtime';

export class AppState {
  @observable user: User | null = null;
  @observable isLoading: boolean = false;
  @observable items: Item[] = [];

  userChanged(newUser: User | null) {
    // React to user changes
    console.log('User changed:', newUser);
  }
}

Store Pattern

import { resolve, IEventAggregator } from '@aurelia/kernel';

export class UserStore {
  private users: User[] = [];

  constructor(private eventAggregator: IEventAggregator = resolve(IEventAggregator)) {}

  async loadUsers() {
    this.users = await this.userService.getUsers();
    this.eventAggregator.publish('users:loaded', this.users);
  }

  addUser(user: User) {
    this.users.push(user);
    this.eventAggregator.publish('user:added', user);
  }

  getUsers(): User[] {
    return [...this.users];
  }
}

import { resolve, IEventAggregator } from '@aurelia/kernel';

export class UserList {
  users: User[] = [];

  constructor(
    private userStore: UserStore = resolve(UserStore),
    private eventAggregator: IEventAggregator = resolve(IEventAggregator)
  ) {}

  binding() {
    this.users = this.userStore.getUsers();
    this.eventAggregator.subscribe('users:loaded', (users: User[]) => {
      this.users = users;
    });
  }
}

Dialog Setup

import { IDialogService } from '@aurelia/dialog';

export class MyComponent {
  constructor(private dialogService: IDialogService = resolve(IDialogService)) {}

  async openDialog() {
    const result = await this.dialogService.open({
      component: () => import('./my-dialog'),
      model: { title: 'Confirm Action' }
    });

    if (!result.wasCancelled) {
      console.log('Dialog result:', result.output);
    }
  }
}

Dialog Component

import { IDialogController } from '@aurelia/dialog';

@customElement({
  name: 'my-dialog',
  template: `
    <div class="dialog">
      <h2>\${model.title}</h2>
      <p>Are you sure you want to continue?</p>
      <button click.trigger="cancel()">Cancel</button>
      <button click.trigger="confirm()">Confirm</button>
    </div>
  `
})
export class MyDialog {
  constructor(private controller: IDialogController = resolve(IDialogController)) {}

  activate(model: any) {
    this.model = model;
  }

  cancel() {
    this.controller.cancel();
  }

  confirm() {
    this.controller.ok('confirmed');
  }
}

HTTP Client

Basic Setup

import { resolve } from '@aurelia/kernel';
import { IHttpClient } from '@aurelia/fetch-client';

export class ApiService {
  constructor(private http: IHttpClient = resolve(IHttpClient)) {}

  async getUsers(): Promise<User[]> {
    const response = await this.http.fetch('/api/users');
    return response.json();
  }

  async createUser(user: User): Promise<User> {
    const response = await this.http.fetch('/api/users', {
      method: 'POST',
      body: JSON.stringify(user),
      headers: { 'Content-Type': 'application/json' }
    });
    return response.json();
  }
}

Service Usage

export class UserManager {
  users: User[] = [];

  constructor(private apiService: ApiService = resolve(ApiService)) {}

  async loadUsers() {
    try {
      this.users = await this.apiService.getUsers();
    } catch (error) {
      console.error('Failed to load users:', error);
    }
  }

  async addUser(userData: Partial<User>) {
    try {
      const newUser = await this.apiService.createUser(userData as User);
      this.users.push(newUser);
    } catch (error) {
      console.error('Failed to create user:', error);
    }
  }
}

HTTP Client Configuration

import { HttpClientConfiguration } from '@aurelia/fetch-client';

export const HttpConfig = {
  register(container: IContainer) {
    container.register(
      HttpClientConfiguration.customize(config => {
        config
          .useStandardConfiguration()
          .withBaseUrl('/api')
          .withDefaults({
            headers: {
              'Content-Type': 'application/json',
              'Accept': 'application/json'
            }
          })
          .withInterceptor({
            request(request) {
              console.log('Request:', request);
              return request;
            },
            response(response) {
              console.log('Response:', response);
              return response;
            }
          });
      })
    );
  }
};

Integration (plugins, shared components, etc)

Migrating from v1

One of the biggest differences compared to Aurelia v1 is the way integrations work.

In v1, you would have a configure function like so:

index.ts (producer)

export function configure(config: FrameworkConfiguration) {
  config.globalResources(['./my-component', './my-component-2']);
}

Which would then be consumed as either a plugin or a feature like so:

main.ts (consumer)

consumer

aurelia.use.plugin('producer');
// or
aurelia.use.feature('./producer');

In v2 the string-based conventions are no longer a thing. We use native ES modules now. And there are no more different APIs for resources, plugins and features. Instead, everything is a dependency that can be registered to a container, its behavior may be altered by specific metadata that's added by framework decorators.

The most literal translation from v1 to v2 of the above, would be as follows:

index.ts (producer)

import { MyComponent } from './my-component';
import { MyComponent2 } from './my-component-2';
export const Producer = {
  register(container: IContainer) {
    container.register(MyComponent, MyComponent2);
  },
};

main.ts (consumer)

consumer

au.register(Producer);

The `register` method

In Aurelia v2, everything (including the framework itself) is glued together via DI. The concept is largely the same whether you're building a plugin, a shared component or a service class.

The producer (or the exporting side) exposes an object with a register method, and the consumer (the importing side) passes that object into its au.register call (for global registration) or into the dependencies array of a custom element (for local registration).

The DI container calls that register method and passes itself in as the only argument. The producer can then register resources / components / tasks to that container. Internally, things like resources and tasks have special metadata associated with them which allows the framework to discover and consume them at the appropriate times.

Below are some examples of how integrations can be produced and consumed:

1.1 Simple object literal with a register method

index.ts (producer)

export const MyPluginConfiguration = {
  register(container: IContainer) {
    container.register(
      ...PluginResources,
      ...PluginComponents,
    );
  },
};

main.ts (consumer)

import { Aurelia } from 'aurelia';

new Aurelia().register(MyPluginConfiguration).app(...);

1.2 A function that returns an object literal with a register method (to pass in e.g. plugin options)

index.ts (producer)

function configure(container: IContainer, config: MyPluginConfig) {
  switch (config.storageType) {
    case 'localStorage':
      container.register(LocalStorageProvider);
      break;
    case 'indexedDB':
    default:
      container.register(IndexedDBProvider);
      break;
  }
}
export const MyPluginConfiguration = {
  register(container: IContainer) {
    configure(container, MyPluginConfig.DEFAULT);
  },
  customize(config: MyPluginConfig) {
    return {
      register(container: IContainer) {
        configure(container, config);
      },
    };
  },
};

main.ts (consumer)

import { Aurelia } from 'aurelia';

new Aurelia().register(MyPluginConfiguration).app(...);
// OR
new Aurelia().register(MyPluginConfiguration.customize({ storageType: 'localStorage' })).app(...)

1.3 An interface

index.ts (producer)

export const IStorageClient = DI.createInterface<IStorageClient>('IStorageClient', x => x.singleton(LocalStorageClient));

Interfaces and classes do not need to be registered explicitly. They can immediately be injected. The container will "jit register" them the first time they are requested.

1.4 A class (typically a resource)

index.ts (producer)

@customElement({ name: 'name-tag', template: `<span>\${name}</span>` })
export class NameTag {}

main.ts (consumer)

To register it as a global resource (available in all components)

import { Aurelia } from 'aurelia';

new Aurelia().register(NameTag).app(...);

OR:

name-list.ts (consumer)

To register it as a local resource (available only in that specific custom element)

export class NameListCustomElement {
  static dependencies = [NameTag];
}
// OR
@customElement({ ..., dependencies: [NameTag] })
export class NameListCustomElement {}

1.5 A (module-like) object with any of the above as its properties

resources/index.ts (producer)

export * from './my-button';
export * from './my-input';
export * from './my-nav';

main.ts (consumer)

import { Aurelia } from 'aurelia';
import * as GlobalResources from './resources';

new Aurelia().register(GlobalResources).app(...);

PreviousSide-by-side comparison NextPlayground

Last updated 1 month ago

Was this helpful?

hashtagCheat Sheet

hashtagMigration quick reference

hashtagBootstrapping

hashtagSimple

hashtagScript tag (Vanilla JS)

hashtagScript tag (Vanilla JS - enhance)

hashtagMulti-root

hashtagAdvanced (low-level)

hashtagAppTask lifecycle hooks and deterministic teardown

hashtagcompat-v1 bridge while migrating

hashtagCustom elements

hashtagWith conventions

hashtagWithout conventions

hashtagVanilla JS

hashtagCustom attributes

hashtagWith conventions

hashtagWithout conventions

hashtagVanilla JS

hashtagTemplate controllers

hashtagWith conventions

hashtagWithout conventions

hashtagVanilla JS

hashtagBinding behaviors

hashtagWith conventions

hashtagWithout conventions

hashtagVanilla JS

hashtagValue converters

hashtagWith conventions

hashtagWithout conventions

hashtagVanilla JS

hashtagAttribute patterns

hashtagBinding commands / instruction renderer

hashtagCSS Classes & Styles

hashtagObservable Properties

hashtagTemplating syntax

hashtagBuilt-in custom attributes & template controllers (AKA directives)

hashtagLifecycle hooks

hashtagMigrating from v1

hashtagThe view model interfaces

hashtagDependency Injection

hashtagMigrating from v1

hashtagCreating an interface

hashtagStrongly-typed with default

hashtagNo default (more loosely coupled)

hashtagInjecting an interface

hashtagRegistration types

hashtagCreating resolvers explicitly

hashtagDecorating classes

hashtagCustomizing injection

hashtagUsing lifecycle hooks in a non-blocking fashion but keeping things awaitable

hashtagExample that blocks rendering (but is simplest to develop)

hashtagExample that does not block rendering and avoids race conditions (without task queue)

hashtagExample that does not block rendering and avoids race conditions (with task queue)

hashtagRouter & Navigation

hashtagRoute Configuration

hashtagNavigation

hashtagRouter Viewports

hashtagRouter Links in Templates

hashtagValidation

hashtagBasic Validation Rules

hashtagValidation Controller

hashtagTemplate Validation Display

hashtagAnimation

hashtagCSS Animations

hashtagWeb Animations API

hashtagRouter Transition Animations

hashtagProgrammatic Animations

hashtagUI Composition

hashtagau-compose

hashtagProgrammatic Composition

hashtagSynthetic Views

hashtagCreating Synthetic Views

hashtagTemplate Controllers with Synthetic Views

hashtagShadow DOM & Slots

hashtagShadow DOM Setup

hashtagUsing Slots

hashtagReplaceable Parts

hashtagUI Virtualization

hashtagVirtual Repeat

hashtagVirtual Repeat Configuration

Cheat Sheet

Migration quick reference

Bootstrapping

Simple

Script tag (Vanilla JS)

Script tag (Vanilla JS - enhance)

Multi-root

Advanced (low-level)

AppTask lifecycle hooks and deterministic teardown

compat-v1 bridge while migrating

Custom elements

With conventions

Without conventions

Vanilla JS

Custom attributes

With conventions

Without conventions

Vanilla JS

Template controllers

With conventions

Without conventions

Vanilla JS

Binding behaviors

With conventions

Without conventions

Vanilla JS

Value converters

With conventions

Without conventions

Vanilla JS

Attribute patterns

Binding commands / instruction renderer

CSS Classes & Styles

Observable Properties

Templating syntax

Built-in custom attributes & template controllers (AKA directives)

Lifecycle hooks

Migrating from v1

The view model interfaces

Dependency Injection

Migrating from v1

Creating an interface

Strongly-typed with default

No default (more loosely coupled)

Injecting an interface

Registration types

Creating resolvers explicitly

Decorating classes

Customizing injection

Using lifecycle hooks in a non-blocking fashion but keeping things awaitable

Example that blocks rendering (but is simplest to develop)

Example that does not block rendering and avoids race conditions (without task queue)

Example that does not block rendering and avoids race conditions (with task queue)

Router & Navigation

Route Configuration

Navigation

Router Viewports

Router Links in Templates

Validation

Basic Validation Rules

Validation Controller

Template Validation Display

Animation

CSS Animations

Web Animations API

Router Transition Animations

Programmatic Animations

UI Composition

au-compose

Programmatic Composition

Synthetic Views

Creating Synthetic Views

Template Controllers with Synthetic Views

Shadow DOM & Slots

Shadow DOM Setup

Using Slots

Replaceable Parts

UI Virtualization

Virtual Repeat

Virtual Repeat Configuration