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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@fransek/next-i18n

v0.5.1

Published

A simple i18n library for Next.js

Readme

@fransek/next-i18n

Version Downloads Minzipped size

A simple and type-safe i18n library for Next.js.

Setup

  1. Install the package:
npm i @fransek/next-i18n
# or
yarn add @fransek/next-i18n
# or
pnpm add @fransek/next-i18n
  1. Create a config file somewhere in your project, e.g. src/i18n/i18nConfig.ts:
import { defineI18nConfig } from "@fransek/next-i18n";

export default defineI18nConfig({
  locales: ["en-US", "en-GB", "it", "sv"],
  defaultLocale: "en-US",
});
  1. Create a file for the server client, e.g. src/i18n/server.ts:
import { createI18nServerClient } from "@fransek/next-i18n";
import i18nConfig from "./i18nConfig";

export const { getContent, getLocale, middleware } =
  createI18nServerClient(i18nConfig);
  1. Create a file for the browser client, e.g. src/i18n/client.ts:
"use client";

import { createI18nClient } from "@fransek/next-i18n";
import i18nConfig from "./i18nConfig";

export const { Content, useContent, useLocale } = createI18nClient(i18nConfig);
  1. Add a middleware.ts file to your src directory and organize your files like this:
src/
|-- app/
|   |-- [locale]/
|   |   |-- layout.tsx
|   |   |-- page.tsx
|-- middleware.ts
  1. Add the following code to your middleware.ts file:
import { middleware } from "./i18n/server";

export default middleware();

export const config = {
  matcher: [
    "/((?!_next|[^?]*\\.(?:html?|css|js(?!on)|jpe?g|webp|png|gif|svg|ttf|woff2?|ico|csv|docx?|xlsx?|zip|webmanifest)).*)",
    "/(api|trpc)(.*)",
  ],
};
  1. Add lang={await getLocale()} to the <html> tag in your layout.tsx file:
import { getLocale } from "@/i18n/server";

export default async function RootLayout({
  children,
}: Readonly<{
  children: React.ReactNode;
}>) {
  return (
    <html lang={await getLocale()}>
      <body>{children}</body>
    </html>
  );
}

Browser Client

useContent

The useContent hook is used to access localized content in your client components.

"use client";

import { useContent } from "@/i18n/client";

const content = {
  "en-US": {
    greeting: "Hello world!",
  },
  "en-GB": {
    greeting: "Hello world!",
  },
  it: {
    greeting: "Ciao mondo!",
  },
  sv: {
    greeting: "Hej världen!",
  },
};

export const ClientComponent = () => {
  const { greeting } = useContent(content);

  return <h3>{greeting}</h3>;
};

useLocale

The useLocale hook is used to access the current locale in your client components.

Content

A thin wrapper component around the useContent hook for in-line localization.

import { Content } from "@/i18n/client";

export const Greeting = () => (
  <h1>
    <Content>
      {{
        "en-US": "Hello world!",
        "en-GB": "Hello world!",
        it: "Ciao mondo!",
        sv: "Hej världen!",
      }}
    </Content>
  </h1>
);

Server Client

getContent

The getContent function is used to access localized content in your server components.

import { getContent } from "@/i18n/server";

const content = {
  "en-US": {
    greeting: "Hello world!",
  },
  "en-GB": {
    greeting: "Hello world!",
  },
  it: {
    greeting: "Ciao mondo!",
  },
  sv: {
    greeting: "Hej världen!",
  },
};

export const ClientComponent = async () => {
  const { greeting } = await getContent(content);

  return <h3>{greeting}</h3>;
};

getLocale

The getLocale function is used to access the current locale in your server components.

middleware

The middleware function is used to handle locale detection and redirection in your Next.js application. It should be exported from your middleware.ts file as shown in the setup instructions.