Comments (10)
@8th-block this one? https://angular.dev/guide/i18n
Yes
from core.
Hi,
I have almost same problem. For your translate pipe error, you have to import TranslateModule in your standalone component. But, then another problem appears. Translation are not loaded for your standalone component. Did you resolve this ?
from core.
No...unfortunately no one answered.
I would like to introduce gradually the standalone component, but This situation prevents me from doing so.
from core.
I think this project went silent time to look for alternatives
from core.
@pretext-mats which alternatives do you recommend ?
from core.
@pretext-mats which alternatives do you recommend ?
I have not got a faintest idea :-) Been using this translate since pre ng 2 ... may be I should not be looking for an alternative quite yet. For the SACs you can still load translation files manually if you want
from core.
I don't know the contents of your SharedModule, but if you're missing the translate pipe in your PricingComponent, then you need to add an import for TranslateModule
, e.g.
@Component({
selector: 'app-pricing',
standalone: true,
imports: [SharedModule, TranslateModule /* added import */],
templateUrl: './pricing.component.html',
styleUrls: ['./pricing.component.scss']
})
export class PricingComponent { }
The TranslateModule consists of component / pipe / directive exports in addition to the providers.
Before migrating your component to standalone, you might have declared the component in the same module where TranslateModule.forChild()
had also been imported, and therefore the pipe was also available to the component.
from core.
I don't know the contents of your SharedModule, but if you're missing the translate pipe in your PricingComponent, then you need to add an import for
TranslateModule
, e.g.@Component({ selector: 'app-pricing', standalone: true, imports: [SharedModule, TranslateModule /* added import */], templateUrl: './pricing.component.html', styleUrls: ['./pricing.component.scss'] }) export class PricingComponent { }The TranslateModule consists of component / pipe / directive exports in addition to the providers. Before migrating your component to standalone, you might have declared the component in the same module where
TranslateModule.forChild()
had also been imported, and therefore the pipe was also available to the component.
Trust me it is not the case. We have tried that already still no joy - many other issues pop up
from core.
I just switched to angular provided i18n module in the end ...
from core.
@8th-block this one?
https://angular.dev/guide/i18n
from core.
Related Issues (20)
- bump angular 17 HOT 3
- Translation keys are ignored when dot format and nested format are mixed
- How to use ngx-translate in Angular 17, Knowing that AppModule is not implemented? HOT 3
- Support for Angular v17 HOT 30
- ngx-translate creates billions of tiny files HOT 1
- Using ngx-translate in a standalone component HOT 4
- 'EventEmitter' and 'DefaultLangChangeEvent' is declared but its value is never read.
- Angular 17 SSR. Standalone implementation - NullInjectorError: No provider for _TranslatePipe! HOT 1
- I am trying to add Arabic language. I have configured package correctly but some labels are translated some are not
- Latency when loading the website, because Translation Key appears when user opens our website HOT 1
- Add opption to pass callback in translate pipe
- ncaught SyntaxError: Cannot use import statement outside a module (at scripts.js:16887:1) main.ts:13 Error: Unexpected value 'TranslateModule' imported by the module 'AppModule'. Please add an @NgModule annotation. at verifySemanticsOfNgModuleDef (core.mjs:28868:5) at core.mjs:28878:5 at Array.forEach (<anonymous>) at verifySemanticsOfNgModuleDef (core.mjs:28876:43) at AppModule.get (core.mjs:28833:23) at getInjectorDef (core.mjs:333:1) at walkProviderTree (core.mjs:5550:1) at core.mjs:5500:6 at core.mjs:4701:1 at Array.forEach (<anonymous>)
- Wrong TranslateHttpLoader after upgrade app to Angular 17
- ngx-translate not working with interceptor in Ionic Capacitor app
- Error: [$injector:unpr] Unknown provider: translateProvider <- translate
- Configuration: defaultLanguage in TranslateModule.forRoot as a Provider HOT 1
- ngx-translate.com is pointing another website HOT 3
- Ngx-translate: ..assets/i18n/ja.json: 404 Not Found after deployment HOT 1
- TranslateService.use with multiple calls causes to display the wrong language
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from core.