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

@conclurer/i18n

v0.0.1

Published

This module allows you to provide translations to an application or module.

Downloads

3

Readme

Internationalization Module

This module allows you to provide translations to an application or module.

Basic Concepts

Internationalization Module uses the following elements to provide translations:

  • LANGUAGE_SCHEMAS allow you to define languages and language models
  • TRANSLATION_SOURCES defines sources for translation files
  • USER_LANGUAGE provides the current user's language
  • TRANSLATION_NAMESPACE provides the namespace of language variables inside feature modules
  • TRANSLATION_LIBRARIES defines third-party libraries that shall be translated along the first-party modules.

How to use

// app.module.ts

import { NgModule } from '@angular/core';
import { InternationalizationModule } from '@conclurer/i18n';

@NgModule({
  imports: [
    InternationalizationModule.forRoot({
      supportedLanguages: [
        {
          code: 'de-de',
          simplifiedCode: 'de',
          pluralization: n => (n === 1 ? 'one' : 'other'),
        },
      ],
      userLanguage: {
        code: 'de-de',
        simplifiedCode: 'de',
      },
      libraryTranslation: [
        locale => {
          // todo translate third-party library on language change
        },
      ],
      translationSources: [
        locale => import(`./_i18n/${locale.simplifiedCode}.json`).then(m => m.default),
      ],
    }),
  ],
})
export class AppModule {}
// de.json
{
  "greeting": "Hallo Welt",
  "messages": {
    "notification": {
      "one": "%{count} Benachrichtigung",
      "other": "%{count} Benachrichtigungen"
    }
  }
}
<!-- <h1>Hallo Welt</h1> -->
<h1>{{ 'greeting' | t }}</h1>
<!-- <p>5 Benachrichtigungen</p> -->
<p>{{ 'messages.notification' | t: {count: 5} }}</p>

Usage in Feature Modules

In feature modules, you should define a special provider that can then be provided directly into the target components.

It is not possible to import feature module providers in NgModuless that are not imported using Angular's router.

This is because Angular attaches child module providers to the root injector.

import { InternationalizationModule } from '@conclurer/i18n';

export const FEATURE_MODULE_TRANSLATIONS = InternationalizationModule.exportedComponentProviders({
  localNamespace: 'featureModuleNamespace',
  translationSources: [
    locale => import(`./feature/_i18n/${locale.simplifiedCode}.json`).then(m => m.default),
  ],
});
// feature/_i18n/de.json
{
  "example": "Feature Module Example"
}
// Feature component

import { Component } from '@angular/core';

@Component({
  providers: [
    FEATURE_MODULE_TRANSLATIONS,
  ],
})
export class FeatureComponent {}
<!-- This uses the global namespace -->
<h1>{{ 'greeting' | t }}</h1>

<!-- Local namespace -->
<!-- <h1>Feature Module Example</h1> -->
<h1>{{ '@.example' | t }}</h1>

<!-- Local lang var, accessed via global namespace -->
<!-- <h1>Feature Module Example</h1> -->
<h1>{{ 'featureModuleNamespace.example' | t }}</h1>