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

@deejayy/runtime-localizer

v18.0.1

Published

Runtime Localizer for Angular

Downloads

39

Readme

npm

Runtime Localizer

Runtime localization was never been easier!

npm i @angular/localize @deejayy/runtime-localizer
  • single build
  • keep translations in a plain simple JSON file
  • have effective fallback values
  • use anywhere (code, template)
  • unlimited languages (even loadable from backend!)
  • setting kept persistent in the localStorage (overrides LOCALE_ID upon initialization)
  • loads before app starts

Setup and usage

1. Add necessary changes to your angular application

Add this line to the beginning of your main.ts:

import '@angular/localize/init';

2. Create language token files (json format)

Put the messages file in your /assets/ folder somewhere. E.g. /assets/messages/messages.en-US.json with the content:

{
  "your-scope/example-token": "Corresponding text"
}

3. Add localizer module to app.module.ts import section

imports: [
  ...
  RuntimeLocalizerModule.forRoot([
    {
      lang: 'en-US',
      path: '/assets/messages/messages.en-US.json',
    },
    {
      lang: 'hu-HU',
      path: '/assets/messages/messages.hu-HU.json',
    },
  ]),
]

4. Place the language token in the template

<div i18n="@@your-scope/example-token">This is the fallback content if language file not found or token is missing.</div>

... or in the code:

public buttonText: string = $localize`:@@button-text:Fallback button text`;

5. Change language, the module will keep it permanent

<button i18n="@@app/button/set-language" (click)="setLang('hu-HU')">Set language to: hu-HU</button>
constructor(private runtimeLocalizerService: RuntimeLocalizerService) {}

public setLang(lang: string) {
  this.runtimeLocalizerService.saveLocale(lang, true);
}

The setting will be saved to the localStorage under the key @deejayy/runtime-localizer/localeId (you can refer it as runtimeLocalizerStorageId from the package).

The second parameter is whether the page should be reloaded by the localizer module (true) or you want to take care of yourself in your application (by default false).

Further reading

Check official angular localization guide for more info.