{ "id": "guide/migration-localize", "title": "$localize Global Import Migration", "contents": "\n\n\n
\n mode_edit\n
\n\n\n
\n

$localize Global Import Migrationlink

\n

What does this schematic do?link

\n

If you're using i18n, this schematic adds an import statement for @angular/localize to polyfills.ts that will look something like this:

\n\n/******************************************************************\n * Load `$localize` - used if i18n tags appear in Angular templates.\n */\nimport '@angular/localize/init';\n\n

It also lists @angular/localize as a dependency in your app's package.json to ensure the import is found.

\n\n\"dependencies\": {\n ...\n \"@angular/localize\": \"...\",\n ...\n}\n\n

@angular/localize is a new package that supports i18n of messages in Ivy applications.\nThis package requires a global $localize symbol to exist.\nThe symbol is loaded by importing the @angular/localize/init module, which has the side-effect of attaching it to the global scope.

\n

Why is this migration necessary?link

\n

Prior to Angular version 9, Angular's internationalization (i18n) system inlined translated messages into the compiled output as part of this template compilation.\nThis approach required running the template compiler once per target locale, often leading to slow production build times.

\n

In the new i18n system, the Angular compiler tags i18n messages in the compiled code with a global $localize handler.\nThe inlining of translations then occurs as a post-compilation step for each locale.\nBecause the application does not need to be built again for each locale, this makes the process much faster.

\n

The post-compilation inlining step is optional—for example during development or if the translations will be inlined at runtime.\nTherefore this global $localize must be available on the global scope at runtime.\nTo make $localize available on the global scope, each application must now import the @angular/localize/init module.\nThis has the side-effect of attaching a minimal implementation of $localize to the global scope.

\n

If this import is missing, you will see an error message like this:

\n\nError: It looks like your application or one of its dependencies is using i18n.\nAngular 9 introduced a global `$localize()` function that needs to be loaded.\nPlease run `ng add @angular/localize` from the Angular CLI.\n(For non-CLI projects, add `import '@angular/localize/init';` to your polyfills.ts file)\n\n

This schematic automatically adds the @angular/localize/init import for you\nif your app uses Angular's i18n APIs.

\n

Why is my tslint failing?link

\n

The import of @angular/localize/init may cause a tslint error for no-import-side-effect because it adds to the global context (that is, a side effect).\nTo fix this error, add the following to your tslint.config:

\n\n\"no-import-side-effect\": [\n true,\n {\n \"ignore-module\": \"(core-js/.*|zone\\\\.js/.*|@angular/localize/init)$\"\n }\n]\n\n

Do I need to change how I write i18n in my Angular templates?link

\n

The template syntax for i18n has not changed, so you will still want to use the i18n attribute as you did before.

\n\n \n
\n\n\n" }