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

@transglot/next

v0.1.0

Published

SSR-aware Next.js 14/15 helpers over @transglot/runtime: a server-side loadTranslations() that returns a serializable snapshot, and a hydration-safe <NextTranslateProvider> (a 'use client' wrapper of @transglot/react-i18n) seeded from that snapshot, with

Readme

@transglot/next

SSR-aware Next.js helpers over @transglot/runtime. Fetch a locale's published bundle on the server, hand the page a serializable snapshot, and hydrate a client provider from it so there is no refetch flash.

  • Server entry @transglot/next has no React import, so it is safe in a React Server Component, a route handler, or getServerSideProps.
  • Client entry @transglot/next/client is the 'use client' boundary: NextTranslateProvider, useTranslations, <T>.

Install

npm install @transglot/next @transglot/runtime

Server: load a snapshot

loadTranslations(options) returns a serializable TranslateSnapshot. Its options are the same CDN coordinates the runtime client takes:

| option | required | meaning | | --- | --- | --- | | baseUrl | yes | origin of the app / CDN, e.g. https://app.example.com | | project | yes | numeric project id (the CDN URL segment) | | cdnKey | yes | read-only taicdn_… key (server-side only; never sent to the browser) | | locale | yes | the locale to fetch | | version | no | pin an immutable …/v{n} version instead of "latest" | | fetchImpl | no | injected fetch (defaults to the global) |

import { loadTranslations } from '@transglot/next';

const snapshot = await loadTranslations({
  baseUrl: 'https://app.example.com',
  project: 42,
  cdnKey: process.env.TRANSGLOT_CDN_KEY!,
  locale: 'en',
});

Client: seed the provider

'use client';
import { NextTranslateProvider, useTranslations, T } from '@transglot/next/client';

export function Providers({ snapshot, children }) {
  return <NextTranslateProvider snapshot={snapshot}>{children}</NextTranslateProvider>;
}

function Title() {
  const { t } = useTranslations();
  return <h1>{t('home.title')}</h1>;
}

The full runtime client contract (the createClient options above, plus t, loadLocale, setLocale, preload, onChange) is documented in @transglot/runtime. createClient and ClientOptions are re-exported here so a host needs only one import.