intlayer-angular

---
name: intlayer-angular
description: Integrates Intlayer internationalization with Angular applications. Use when the user asks to "setup Angular i18n", create a new translated component, use the "useIntlayer" composable, or configure providers.
metadata:
  author: Intlayer
  url: https://intlayer.org
  license: Apache-2.0
  mcp-server: "@intlayer/mcp"
  category: productivity
  tags: [i18n, angular]
  documentation: https://intlayer.org/doc
  support: contact@intlayer.org
---

# Intlayer Angular Usage

## Core Philosophy

Intlayer promotes **Component-Level Content Declaration**. Instead of a massive global translation file, content is declared in `*.content.ts` files adjacent to the Angular components that use them.

## Workflow

To create a translated component, you need two files:

1.  **Declaration:** A content file (e.g., `my-component.content.ts`) defining the dictionary.
2.  **Implementation:** An Angular component (e.g., `my-component.component.ts`) using the `useIntlayer` signal.

### 1. Declare Content

Create a content file using `t()` for translations.
**File:** `src/app/my-component/my-component.content.ts`

```typescript
import { t, type Dictionary } from "intlayer";

const content = {
  // The 'key' must be unique and matches what you pass to useIntlayer()
  key: "my-component",
  content: {
    text: t({
      en: "Welcome",
      fr: "Bienvenue",
      es: "Hola",
    }),
  },
} satisfies Dictionary;

export default content;
```

## Setup

- [Angular](references/environment_angular.md)
- [Angular 19](references/environment_angular_19.md)
- [Analog](references/environment_analog.md)

Register `provideIntlayer()` in the `providers` of your `ApplicationConfig` (see the [Angular guide](references/environment_angular.md)).

## useIntlayer Hook

In Angular, `useIntlayer` returns a **Signal**. You must call it as a function to access the value.

```typescript
import { Component } from "@angular/core";
import { useIntlayer } from "angular-intlayer";

@Component({
  selector: "app-my-component",
  standalone: true,
  template: `
    <div>
      <h1>
        {{ content().text }}
      </h1>
      <img [src]="content().text.value" [alt]="content().text.value" />
    </div>
  `,
})
export class MyComponent {
  content = useIntlayer("my-component");
}
```

## Bundle Optimization

Read content fields by name (dot access or destructuring) so the build can purge and minify the dictionary. Never index content at runtime (`content.statuses[status]`, use `select()`), and call `useIntlayer` in each child component instead of passing content as a prop. See the `intlayer-bundle-optimization` skill.

## Compiler

The [Intlayer Compiler](references/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.

## References

- [Website](https://intlayer.org)
- [Doc](https://intlayer.org/doc)

### Environments

- [Angular](references/environment_angular.md)
- [Angular 19](references/environment_angular_19.md)
- [Analog](references/environment_analog.md)

### Concepts

- [Variants](references/concept_variants.md)
- [Collections](references/concept_collections.md)
- [Compiler](references/compiler.md)
- [Formatters (number, currency, date, …)](references/formatters.md)

### Packages

- [Angular Intlayer Exports](references/packages_angular-intlayer_exports.md)
- [Intlayer Exports](references/packages_intlayer_exports.md)
- [angular-intlayer usePathname](references/packages_angular-intlayer_usePathname.md)

• LICENCE.md 11 KB
• SKILL.md 3 KB
• references/compiler.md 15 KB
• references/concept_collections.md 6 KB
• references/concept_variants.md 21 KB
• references/environment_analog.md 27 KB
• references/environment_angular.md 29 KB
• references/environment_angular_19.md 29 KB
• references/formatters.md 17 KB
• references/packages_angular-intlayer_exports.md 4 KB
• references/packages_angular-intlayer_usePathname.md 4 KB
• references/packages_intlayer_exports.md 12 KB