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

@sanvika/lang

v0.8.1

Published

Sanvika ecosystem Lang platform SDK — consumer i18n + server/admin Cloud clients. Indian-12 + Global-60, contentHash-aware runtime cache, segment lazy loading, RTL, voice codes.

Downloads

509

Readme

@sanvika/lang

Version: 0.8.1
Centralized Lang platform SDK for the Sanvika ecosystem. Consumer i18n (Indian-12 / Global-60), contentHash-aware runtime cache, plus additive server/admin Cloud clients.
Rules: docs/sanvika-eco-system/Lang/very-strict-rules.md

Table of Contents

  1. Kya hai
  2. Install
  3. Quick Start (Indian 12)
  4. Quick Start (Global 60)
  5. API
  6. Server Translations
  7. Platform clients (0.8.0)
  8. Migration
  9. Migration from raw i18next setup

Kya hai

Har Sanvika project mein i18n ka same boilerplate (200-700 lines, 192-560+ JSON imports) repeat ho raha tha. Yeh SDK us boilerplate ko single config call mein collapse karta hai. JSON files project mein hi rehti hain (project-owned), engine yahan se aata hai.

Install

pnpm add @sanvika/lang i18next react-i18next

Quick Start (Indian 12)

// src/utils/language/i18n.js
import { createSanvikaI18n, LANGUAGE_PRESETS } from "@sanvika/lang";

import enNavigation from "./translations/segments/en/navigation.json";
import hiNavigation from "./translations/segments/hi/navigation.json";
// ... other core segment imports

import enDashboard from "./translations/segments/en/dashboard.json";
import hiDashboard from "./translations/segments/hi/dashboard.json";
// ... other lazy segment imports

const { i18n, ensureTranslationSegment } = createSanvikaI18n({
  languages: LANGUAGE_PRESETS.INDIAN_12,
  defaultLanguage: "en",
  fallbackLanguage: "en",
  storageKey: "language",
  coreSegments: {
    en: { ...enNavigation /* , ...enUiCommon, ... */ },
    hi: { ...hiNavigation /* , ...hiUiCommon, ... */ },
  },
  lazySegments: {
    dashboard: { en: enDashboard, hi: hiDashboard },
  },
});

export default i18n;
export { ensureTranslationSegment };

Quick Start (Global 60)

import { createSanvikaI18n, LANGUAGE_PRESETS } from "@sanvika/lang";

const { i18n, ensureTranslationSegment } = createSanvikaI18n({
  languages: LANGUAGE_PRESETS.GLOBAL_60,
  defaultLanguage: "hi",
  fallbackLanguage: "en",
  coreSegments: { /* ... */ },
  lazySegments: { /* ... */ },
});

API

createSanvikaI18n(options)

Returns { i18n, ensureTranslationSegment, getCurrentLanguage }.

| Option | Type | Required | Default | |---|---|---|---| | languages | Array | yes | — | | coreSegments | Object | yes | — | | lazySegments | Object | no | {} | | defaultLanguage | string | no | "en" | | fallbackLanguage | string | no | "en" | | storageKey | string | no | "language" | | i18nextOptions | Object | no | {} |

<LanguageProvider validLanguages={[...]}>

Wraps your app, exposes useLanguage() hook with { currentLanguage, changeLanguage }. Auto-applies dir="rtl" for Urdu/Arabic.

Voice / Flag helpers

import {
  getVoiceLanguageCode,    // "hi" → "hi-IN"
  getFlagEmoji,             // "hi" → "🇮🇳"
  getNativeName,            // "ta" → "தமிழ்"
  isRTLLanguage,            // "ur" → true
  applyLanguageDirection,
  getSupportedLanguages,
} from "@sanvika/lang";

normalizeTranslationArray(value)

Coerces JSON list-like values (object → array, single → array, etc.) into proper arrays.

Server Translations

// src/utils/language/getTranslations.js
import { createServerTranslations } from "@sanvika/lang";
import enNavigation from "./translations/segments/en/navigation.json";
import hiNavigation from "./translations/segments/hi/navigation.json";

const { getTranslations, getServerLocale } = createServerTranslations({
  segmentDataMap: {
    navigation: { en: enNavigation, hi: hiNavigation },
  },
  validLocales: ["en", "hi", "ta", "te", "kn", "ml", "bn", "mr", "gu", "pa", "or", "ur"],
  fallbackLocale: "en",
});

export { getTranslations, getServerLocale };

Runtime cache (0.8.1)

createFetcherBackend compares manifest contentHash to the local cache entry before each namespace GET.

| Case | Behaviour | |---|---| | Hash identical | Skip network — return cached data | | Hash different / missing | GET namespace → replace cache { contentHash, data } | | Network failure | Fall back to last cached data (offline) |

Cache key unchanged: sanvika-lang:{clientId}:{namespace}:{locale} (localStorage by default).

Optional durable storage (React Native):

import AsyncStorage from "@react-native-async-storage/async-storage";
import { createFetcherBackend } from "@sanvika/lang/client";

createFetcherBackend({
  apiUrl, clientId, namespaces,
  storage: {
    getItem: (k) => AsyncStorage.getItem(k),
    setItem: (k, v) => AsyncStorage.setItem(k, v),
  },
});

ETag / If-None-Match: not implemented in the SDK (intentional). Cloud already supports ETag/304; after contentHash skip the hot path does not hit the network. Adding If-None-Match would duplicate the skip decision and add 304→cache handling with little benefit.

Platform clients (0.8.0+)

Additive only. Existing imports are unchanged.

@sanvika/lang/serverLangServerClient (S2S)

import { LangServerClient, createServerTranslations } from "@sanvika/lang/server";

const lang = LangServerClient.fromProcessEnv();
await lang.bulkUpsert({ namespace: "legal", locale: "en", data });
await lang.getManifest();
await lang.getNamespace("navigation", { locale: "hi", fallback: "en" });

@sanvika/lang/adminLangAdminClient (Bearer SuperAdmin JWT)

import { LangAdminClient } from "@sanvika/lang/admin";

const admin = new LangAdminClient({
  baseUrl: process.env.LANG_URL,
  accessToken: jwt, // from @sanvika/auth
});
await admin.importNamespace(clientId, "legal", { locale: "en", data });
await admin.listClients();

@sanvika/lang/client — side-effect-free fetcher

import { createFetcherBackend, clearLocalFetcherCache } from "@sanvika/lang/client";
// Does not auto-init projectI18n (unlike importing @sanvika/lang main entry)

Other additive paths

| Path | Exports | |---|---| | @sanvika/lang/react | LanguageProvider, useLanguage | | @sanvika/lang/contracts | LangError, DEFAULT_LANG_URL, ENDPOINTS, validators |

Migration

No migration required.

Upgrade to @sanvika/[email protected]. All existing imports continue to work without code changes. Runtime cache is transparent (same keys; hash compare is additive). Server/admin/client paths from 0.8.0 remain available.

Migration from raw i18next setup

| Before (per project) | After | |---|---| | 700-line i18n.js with 192/560+ static imports + manual resources, segmentLoaders, loadedSegments, ensureTranslationSegment | 1 createSanvikaI18n(...) call | | Hand-written voiceCodeMapper.js per project | Built-in (getVoiceLanguageCode, getFlagEmoji, etc.) | | Hand-written LanguageProvider/useLanguage per project | Built-in | | Hand-written getTranslations SSR helper per project | createServerTranslations(...) |