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

svelte-compile-intl

v0.0.0

Published

Svelte's tooling to support internationalization

Downloads

2

Readme

svelte-compile-intl

This project's goal is to provide the tools needed to add super lightweight translations using the ICU format to your application. It is made with svelte in mind, but it could be used in other projects too by using the babel plugin directly.

Becareful though, if you are to use this project, this means that you need to understand how your current tooling works to export multiple bundle with different babel configurations. And your server/SSG should be aware of these different bundles in order to serve the correct bundle to your users.

Related projects

If you are willing to add translations to your application but don't want to change too much your compilation pipeline, I suggest to have a look at svelte-i18n or svelte-intl instead.

Installation

Install svelte-compile-intl from github by using:

npm install --save JulienPradet/svelte-compile-intl

Configure your pipeline

Change your tooling pipeline to run the compilation once for each language in your application. Once this is done, you can add the compilation from svelte-comile-intl either by:

  • Using a rollup plugin (only if you don't already have Babel in your pipeline):

    // rollup.config.js
    + const path = require("path");
    
    module.exports = {
      input: "src/index.js",
      plugins: [
    +    rollupCompileIntlPlugin(
    +      "fr-FR",
    +      path.join(process.cwd(), `translations`)
    +    ),
      ],
    }
  • Using the babel plugin directly (if Babel is already configured in your compilation tooling)

    + const path = require("path");
    
    module.exports = {
      presets: [
        [
          "@babel/preset-env",
          {
            targets: {
              esmodules: true,
            },
          },
        ],
    +    [
    +      "svelte-compile-intl/babel-plugin",
    +      {
    +          locale: "fr-FR",
    +          translationsFolder: path.join(process.cwd(), `translations`)
    +      }
    +    ]
      ],
    };

Once you've set it up, this means that you will have access to a translations folder at the root of your application that will be created on first compilation. It will then be updated each time a new translation is added. Once you've compiled your application in different languages, each locale will have its own JSON file in this folder.

Usage in your Svelte application

At the root of your application, define the current locale:

import { setCurrentLocale } from "svelte-compile-intl";
setCurrentLocale("fr-FR");

However, since the locale should be different for each build, I either suggest you to use something like @rollup/plugin-replace or by injecting a global variable from your server (<script>window.locale = "fr-FR";</script>).

Once this is done, you can declare new translations in your file like this:

<script>
  import { _ } from "svelte-compile-intl";
</script>

<h1>{_("Hello world")}</h1>

You can then go to your translations/fr-FR.json file and set it like this:

{
  "Hello world": "Bonjour le monde"
}

Advanced usecases

Call _ in javascript

You can use the translation mechanism in your javascript too. You are not limited by svelte's features.

<script>
  import { _ } from "svelte-compile-intl";
  const hello = _("Hello world")
</script>

<h1>{hello}</h1>

Using other ICU formats

It is possible to use any kind of formats from the ICU standard. Please refer to IntlMessageFormat for full details. But here is a short cheatsheet for the most common cases:

Plural

_("{quantity, plural, =0 {none} =1 {one item} other {# items}}", {
  quantity: 5,
});

Number

// In your main file, add the number formats you want to support
// Please refer to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat#Using_options for format details
import { setCurrentLocale } from "svelte-compile-intl";
setCurrentLocale("fr-FR", {
  number: {
    price: {
      style: "currency",
      currency: "EUR",
    },
  },
});

// In the file containing the translation, you can use the new format (here "price")
import { _ } from "svelte-compile-intl";
_("Your item will cost {priceValue, number, price}", {
  priceValue: 5,
});

// You can also use only the formatting directly
import { formatNumber } from "svelte-compile-intl";
formatNumber(new Date(), "short");

Date

// In your main file, add the date formats you want to support
// Please refer to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat#Using_options for format details
import { setCurrentLocale } from "svelte-compile-intl";
setCurrentLocale("fr-FR", {
  date: {
    short: {
      year: "numeric",
      month: "numeric",
      day: "numeric",
    },
  },
});

// In the file containing the translation, you can use the new format (here "short")
import { _ } from "svelte-compile-intl";
_("Today is {today, date, short}", {
  today: new Date(),
});

// You can also use only the formatting directly
import { formatDate } from "svelte-compile-intl";
formatDate(new Date(), "short");

Time

// In your main file, add the time formats you want to support
// Please refer to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat#Using_options for format details
import { setCurrentLocale } from "svelte-compile-intl";
setCurrentLocale("fr-FR", {
  time: {
    short: {
      hour: "numeric",
      minute: "numeric",
    },
  },
});

// In the file containing the translation, you can use the new format (here "short")
import { _ } from "svelte-compile-intl";
_("It's {today, time, short}", {
  today: new Date(),
});

// You can also use only the formatting directly
import { formatTime } from "svelte-compile-intl";
formatTime(new Date(), "short");

Polyfill

Some Intl APIs are not always available in Node or in some browsers. Please make sure to load the correct polyfills when needed. You can refer to FormatJS's polyfills.

Acknownledgement

This library is a slighlty different take from @cibernox's take on precompilation for svelte-i18n. You can see his original PR here: https://github.com/kaisermann/svelte-i18n/pull/41

This work is also made possible thanks to the huge work of @longlho on FormatJS and more specifically by making the parser available for other libraries.

And finally, in order to do this stuff at compile time, the svelte-compile-intl relies on Babel mostly.