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

sveltekit-translate

v1.0.0

Published

An i18n library designed to be easy to use. It's all still very basic, so if it is lacking certain features, feel free to add some PRs.

Downloads

87

Readme

Sveltekit Translate

An i18n library designed to be easy to use. It's all still very basic, so if it is lacking certain features, feel free to add some PRs.

The syntax for normal usage is nice and compact. The settings and translations are contained in the context of the <Translate /> component. Translating strings can be done with either a component or a function.

The <Tx /> component

The <Tx /> component takes either a html or a text property to locate the string. Optionally a params property can be given for interpolation. For example <Tx text="title" />, or <Tx html="page.header.subtitle" params={someObject} />. The former shows text, the latter parses HTML (without sanitizing).

Note that attributes (e.g. alt texts) cannot be translated with this method.

Translations from functions

If you want to translate attributes, or just prefer using functions, you can also use the $t(path: string, params?: any) function. Note that the params parameter is optional.

The same examples as above can be achieved by doing this: { $t('title') }; and {@html $t('page.header.subtitle') }.

HTML Sanitization

From version 1, I've removed html sanitization as it is becoming harder to support it. I might build it back at some point if there's enough questions for it.

Features

  • 🛩️ Use any JSON file or JS object as input
  • 🛰️ Supports unlimited languages
  • 🛺 Interpolate parameters
  • 🐒 Fallback to the default language for missing values in the current language
  • 🚀 Svelte Stores are used a lot (Everything is reactive)
  • 🦄 Typescript native

Install

npm i -D sveltekit-translate

Live demo

Demo

Sample Code

Sample code for all the basic features can be found here.

Basic Example

In your +layout.svelte create the setup:

<script lang="ts">
	import Translate from 'sveltekit-translate/translate/Translate.svelte';
	import type { TranslateOptions } from 'sveltekit-translate/translate/translateStore';

	let opts: TranslateOptions = {
		defaultLang: 'en', //Set your default (or fallback) language
		currentLang: 'nl' //Set your current language
	};

	//Initial translation data. This could of course be fetched from somewhhere.
	//The library doesn't care how you get the translations.
	let data = {
		en: { title: 'Hello { name }', greeting: 'You are <b>the best!</b>' },
		nl: { title: 'Hoi { name }', greeting: 'Jij bent een <b>toppertje!</b>' },
		es: { title: 'Hola { name }', greeting: 'Eres <b>asombrosa!</b>' }
	};
</script>

<Translate {opts} {data}>
	<slot />
</Translate>

Now you can translate anything in your app by using the <Tx /> component:

<script lang="ts">
	import Tx from 'sveltekit-translate/translate/tx.svelte';

	let name = 'world';
</script>

<div class="my-2">
	<label>
		name
		<input type="text" bind:value="{name}" class="py-2 px-4 ml-2 border rounded" />
	</label>
</div>

<h1 class=" mt-4 mb-2 font-bold text-2xl">
	<Tx text="title" params="{{" name }} />
</h1>
<p>
	<Tx html="greeting" />
</p>

The <Translate /> component creates a context called svelte-translate that contains a SvelteTranslate interface:

const {
    options, // Writable store with the basic options
    translations, //Readible store with the translations object of the current language.
    defaultTranslations // Readible store with the translations object of the default language.
    allLanguages, // Readible string array of all languages we have translations for
    allTranslations, // Writable store containing all of the translations. Also container a convenience method `setLang()` to set or update an existing language.
  } = getContext<SvelteTranslate>(CONTEXT_KEY);

Example for language buttons:

<script lang="ts">
  import { getContext } from 'svelte';
  import { CONTEXT_KEY, type SvelteTranslate } from 'sveltekit-translate/translate/translateStore';

  let { allLanguages, options } = getContext<SvelteTranslate>(CONTEXT_KEY);
</script>

{#each $allLanguages as lang}
  <button
    class="btn px-4 py-2 mr-2 border rounded"
    class:active={$options.currentLang === lang}
    on:click={() => ($options.currentLang = lang)}>{lang}</button
  >
{/each}

<style>
  .btn {
    min-width: 5rem;
  }

  .active {
    @apply bg-sky-400;
  }
</style>

Contributing

Feel free to send PRs or create issues.