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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@angular-translation-service/core

v0.3.4

Published

Signal-based Angular i18n library with runtime language switching and SSR hydration

Readme

@angular-translation-service/core

Signal-based Angular i18n library with runtime language switching and SSR hydration.

Features

  • Signal-first API — reactive translate()/select() plus synchronous instant()
  • Lazy namespace loading — Load translations on-demand per route/component
  • Crash-proof templates — Recursive proxy prevents errors while namespaces load
  • SSR/SSG hydration — Zero-config TransferState integration via /ssr entry point
  • TranslatePipe — Drop-in pipe for template usage
  • Zoneless support — Works with Angular's zoneless change detection

Quick Start

npm install @angular-translation-service/core
import { provideTranslation, httpLoader } from '@angular-translation-service/core';

export const appConfig = {
  providers: [
    provideTranslation({
      defaultLang: 'en',
      supportedLangs: ['en', 'pt-BR'],
      coreNamespaces: ['common'],
      loader: httpLoader('/i18n'),
    }),
  ],
};
import { TranslationService } from '@angular-translation-service/core';

@Component({
  template: `
    @let t = common();
    <h1>{{ t?.nav?.home }}</h1>
  `,
})
export class MyComponent {
  private readonly i18n = inject(TranslationService);
  protected readonly common = this.i18n.select('common');
}

Reactivity

Use translate() and select() for UI that must update after language switches. instant() is deliberately non-reactive and should be reserved for imperative reads such as logs, confirm prompts, or already-loaded toast messages.

protected readonly options = computed(() => [
  { value: 'compact', label: this.i18n.translate('settings:density.compact')() },
  { value: 'comfortable', label: this.i18n.translate('settings:density.comfortable')() },
]);

If instant() is called for a lazy namespace that has never been requested, dev mode warns once and starts loading that namespace. The current synchronous call still returns ''; call ensureNamespaces() first when imperative text must be available immediately.

Typed Keys

The runtime API is permissive by default. When @angular-translation-service/cli generates an i18n.generated.ts file, it augments TranslationKeyRegistry so translate(), instant(), and select() become typed from your JSON packs.

this.i18n.translate('common:nav.home'); // OK
this.i18n.translate('common:nav.hmoe'); // TypeScript error after ats generate

Interpolation

Use {param} as the canonical placeholder form in JSON values. {{param}} remains supported for compatibility.

{ "greeting": "Hello, {name}!" }

SSR

// app.config.server.ts
import { provideTranslationSSR } from '@angular-translation-service/core/ssr';

const serverConfig = {
  providers: [
    provideTranslationSSR({
      resolveLanguage: (req) => req.headers['accept-language']?.split(',')[0] ?? 'en',
    }),
  ],
};

Documentation

Full docs: angular-translation-service.pages.dev

License

MIT