Polyglot detects @jsverse/transloco, rewrites templates to transloco pipes, wires TranslocoPipe into standalone components, and injects TranslocoService for logic strings.
Polyglot detects Transloco from your dependencies (@jsverse/transloco, legacy @ngneat/transloco) and emits Transloco-native code throughout.
<h1>Welcome back</h1>
<p>Your projects are ready</p><h1>{{ 'src.app.app.component.welcome_back' | transloco }}</h1>
<p>{{ 'src.app.app.component.your_projects_are_ready' | transloco }}</p>The same Angular guarantees apply as for every pipe library:
[attr.name]="'key' | transloco" bindings that compile on any element.TranslocoPipe in the decorator's imports: — proven-standalone components only; NgModule apps are left to their existing TranslocoModule wiring.TranslocoService with idempotent constructor injection.{
"src": {
"app": {
"app": {
"component": {
"welcome_back": "Welcome back",
"your_projects_are_ready": "Your projects are ready"
}
}
}
}
}{
"src": {
"app": {
"app": {
"component": {
"welcome_back": "Willkommen zurück",
"your_projects_are_ready": "Ihre Projekte sind bereit"
}
}
}
}
}{
"src": {
"app": {
"app": {
"component": {
"welcome_back": "Bon retour",
"your_projects_are_ready": "Vos projets sont prêts"
}
}
}
}
}No Transloco installed and none forced in config? Every string is flagged with install guidance instead of wrapped — Polyglot never emits calls to a runtime that isn't there. Every file is re-parsed before write, and the run ends with wiring verification:
$ curl -fsSL https://getpolyglot.ai/install.sh | bash
$ polyglot init --framework angular
$ polyglot scan
$ polyglot wrap
$ polyglot translate --languages de # 50 strings free, no signupStart in your terminal
Install the CLI, run a scan, and see exactly what you're missing. Free, no account required.