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

i18next-svelte-scanner

v0.0.4

Published

i18next Svelte scanner

Downloads

36

Readme

i18next Scanner for Svelte

This is i18next scanner for Svelte.

Installation

npm i -D i18next-svelte-scanner

Usage

Sample usage might look like this:

npx i18next-svelte-scanner -s src -o l10n.json

Expected l10n format

Current implementation assumes that l10n is done via function named _ (but most probably you will use it in $_ more frequently.

Here are some example how l10n might look like in Svelte:


// placeholder for translatable string identified by key only
$_('key')

// placeholder for translatable string identified by key and having default value
$_('key', 'default value')

// placeholder for translatable string identified by key that is pluralized
$_('pages', { count: pages })

// placeholder for translatable string that has defaultValue and expects more parameters
$_('error', {
    defaultValue: 'Error in file "{{name}}"',
    name: filename,
})

Sample i18next usage in Svelte

Here is sample how to create _ in i18next using Svelte.

import { writable } from 'svelte/store';
import i18next from 'i18next';

function createL10nStore() {
    const { subscribe, update } = writable(i18next.t);

    async function init() {
        let resources = {}; // TODO: get resources here. Can be read from file, downloaded from service and etc.

        let t = await i18next.init({
            lng: 'en',
            resources,
        });
        update(_t => t);
    }

    async function changeLanguage(lang) {
        let t = await i18next.changeLanguage(lang);
        update(_t => t);
    }

    return {
        subscribe,
        init,
        changeLanguage,
    };
}

export const _ = createL10nStore();