npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ngx-dy-i18n

v0.0.3

Published

The internationalization (i18n) little hack to use native i18n translations in controller

Downloads

27

Readme

ngx-dy-i18n simple hack to use translations in controller with native i18n solution, without using other library for i18n(ngx-translate , ...) it support grouped translations

Usage

1. Import the I18NModule:

You have to import I18NModule.forRoot() in the root NgModule of your application. The forRoot static method is a convention that provides and configures services at the same time. Make sure you only call this method in the root module of your application, most of the time called AppModule.

import {BrowserModule} from '@angular/platform-browser';
import {NgModule} from '@angular/core';
import {I18NModule} from 'ng-dy-i18n';

@NgModule({
    imports: [
        BrowserModule,
        TranslateModule.forRoot()
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }

2. add some translations:

1. Directly in AppComponent using directive
<dyTranslateToken id="title" value="nice title" i18n-value></dyTranslateToken>
<dyTranslateToken id="errors">
  <dyTranslateToken id="notFound" value="page not found" i18n-value></dyTranslateToken>
  <dyTranslateToken id="unknown" value="unknown error" i18n-value></dyTranslateToken>
</dyTranslateToken>
2. Using another component for all translation using component loader
  • add new dummy component
    ng g component I18nTexts
  • add it to entryComponents list
    ...
    entryComponents: [
      I18nTextsComponent
    ]
    ...
  • Inject DyTranslateService in bootstrapped component usually AppComponent
    import {DyTranslateService} from 'ng-dy-i18n';
    ...
    constructor(private tr: DyTranslateService) {}
    ...
  • One time load the translations
         
      ...
       ngOnInit(): void {
          this.tr.addTranslationFromComponent(I18nTextsComponent);
        }
      ...

3. Get the translations:

to get the translations you have to use the provided service DyTranslateService

    
    this.tr.get('alert.title').subscribe(value => {
      alert(value)
    });
    
don't forget to unsubscribe to avoid the memory leaks