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

@sveltebuilder/hermes

v0.0.7

Published

Framework-agnostic, synchronous i18n dictionary store for Svelte 5 — types, load/merge, localText lookup, and a LocalText component.

Readme

@sveltebuilder/hermes

Framework-agnostic i18n primitives for SvelteBuilder. Hermes is a pure, synchronous, in-memory dictionary store — it has no database calls, no fetch, and no async of any kind. Your app loads translated content from wherever it lives and hands it to hermes; hermes only resolves lookups.

Install

npm install @sveltebuilder/hermes

Requires Svelte 5.

Usage

Load a dictionary payload once (typically in your root layout, after fetching it from your database):

import { load } from '@sveltebuilder/hermes';

load(dictionaryPayload, userLocaleCode, fallbackLocaleCode);

Read values with localText, or render them with the <LocalText /> component:

<script lang="ts">
  import { localText, LocalText } from '@sveltebuilder/hermes';
</script>

<h1>{localText('app.title')}</h1>
<LocalText slug="buy_label" scope="product" entityId={product.id} />

localText(slug, scope?, entityId?) resolves a dictionary key built from those three parts:

| Call | Key | | ------------------------------------------ | ---------------------------- | | localText('app.title') | app.title | | localText('buy_label', 'product') | product:buy_label | | localText('product.title', 'product', 42)| product:product.title:42 |

scope is omitted for global/application-level copy and set to the owning entity's table/model name for entity-bound copy.

API

  • load(payload, userLocaleCode, fallbackLocaleCode) — replaces the entire in-memory dictionary. Resolves each key by locale priority: user locale → fallback locale → first available.
  • merge(payload, userLocaleCode, fallbackLocaleCode) — resolves and merges additional entries into the existing dictionary without clearing it (useful for lazy-loading entity copy on route navigation).
  • localText(slug, scope?, entityId?) — reads a resolved string from the dictionary.
  • <LocalText slug scope? entityId? /> — Svelte component wrapper around localText.

Types

Locale, LocalText (record shape, re-exported as LocalTextRecord to avoid clashing with the component), LocalTextLink, Dictionary, DictionaryPayload.

Part of the SvelteBuilder ecosystem

Hermes is the single source of i18n primitives shared across every SvelteBuilder package — @sveltebuilder/coreui and all domain modules import types and localText from here rather than redeclaring them. See the SvelteBuilder README for the full architecture.