aymericzip/intlayer-skills/intlayer-vanilla

Intlayer Vanilla JS Usage

Core Philosophy

Intlayer promotes Component-Level Content Declaration. Instead of a massive global translation file, content is declared in *.content.ts files adjacent to the scripts that use them.

vanilla-intlayer mirrors the react-intlayer API without depending on a UI framework: a pub/sub singleton plus callback-based helpers.

Declare Content

File: src/app.content.ts

import { t, type Dictionary } from "intlayer";
const content = {
  key: "app",
  content: {
    title: t({
      en: "Welcome",
      fr: "Bienvenue",
      es: "Hola",
    }),
  },
} satisfies Dictionary;
export default content;

Setup

• Vite and Vanilla JS (bundled app)
• Vanilla JS (no bundler, standalone script generated by intlayer standalone)

Call installIntlayer() before any content is rendered.

useIntlayer

useIntlayer(key, locale?) returns the content directly. Chain .onChange() to re-render when the locale changes.

import { useIntlayer } from "vanilla-intlayer";
const title = document.querySelector("h1")!;
const content = useIntlayer("app").onChange((newContent) => {
  title.textContent = String(newContent.title);
});
title.textContent = String(content.title);
// Native attributes: use `.value`
// image.alt = content.title.value;

Without a bundler, read the same helpers from the globals of the standalone bundle: window.VanillaIntlayer and window.Intlayer.

useLocale

import { useLocale } from "vanilla-intlayer";
const { locale, availableLocales, setLocale, subscribe } = useLocale();
const unsubscribe = subscribe((newLocale) => {
  document.documentElement.lang = newLocale;
});
setLocale("fr");

Compiler

The Intlayer Compiler can extract all your content keys from your components, using one CLI command (npx intlayer extract) or automatically at app build.

References

• Website
• Doc

Environments

• Vite and Vanilla JS
• Vanilla JS

Concepts

• Variants
• Collections
• Compiler
• Formatters (number, currency, date, …)

Packages

• Intlayer Exports