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

@sonenta/next

v1.0.1

Published

Official Next.js binding for Sonenta i18n — App Router server translations (RSC, fetch-cache) + client provider, on @sonenta/i18n-core + @sonenta/react-i18next.

Readme

@sonenta/next

Official Next.js binding for Sonenta i18n — App Router Server Components + Client Components, on the shared @sonenta/i18n-core engine (server) and @sonenta/react-i18next (client).

Beta (0.1.x). App Router first; Pages Router works via the same server helpers. next, react, i18next, react-i18next are peers.

npm install @sonenta/next i18next react-i18next

Server Components (App Router)

// app/[locale]/page.tsx  (Server Component)
import { getTranslations } from "@sonenta/next/server";

const config = {
  token: process.env.SONENTA_API_KEY!,
  projectUuid: "your-project-uuid",
  defaultLocale: "fr",
  revalidate: 3600, // Next data-cache (ISR) for the CDN fetch
};

export default async function Page({ params: { locale } }: { params: { locale: string } }) {
  const { t } = await getTranslations(config, locale);
  return <h1>{t("home.title")}</h1>;
}

Server resolution reuses the same engine as every Sonenta binding, so it matches the client exactly (interpolation, plurals, fallback).

Client Components

Hydrate the client provider from the server snapshot — no client refetch:

// app/[locale]/layout.tsx (Server Component)
import { getBundles } from "@sonenta/next/server";
import { Providers } from "./providers";

export default async function Layout({ children, params: { locale } }) {
  const initialBundles = await getBundles(config, locale);
  return <Providers locale={locale} initialBundles={initialBundles}>{children}</Providers>;
}
// app/[locale]/providers.tsx
"use client";
import { SonentaProvider } from "@sonenta/next/client";

export function Providers({ locale, initialBundles, children }: any) {
  return (
    <SonentaProvider
      token={process.env.NEXT_PUBLIC_SONENTA_API_KEY!}
      projectUuid="your-project-uuid"
      defaultLocale={locale}
      initialBundles={initialBundles}
    >
      {children}
    </SonentaProvider>
  );
}
// any "use client" component
"use client";
import { useTranslation } from "@sonenta/next/client";
export function Cta() {
  const { t } = useTranslation();
  return <button>{t("cta.start")}</button>;
}

License

MIT © Sonenta