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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@drawilet/nextjs-i18n

v0.0.14

Published

Simplify Next.js internationalization with our client-side package. Seamlessly integrate and access translated content in your project with ease.

Downloads

3

Readme

⬛ nextjs-i18n

Simplify Next.js internationalization with our client-side companion to Node-i18n. Seamlessly integrate and access translated content in your project with ease.

Installation

# npm
npm install @drawilet/nextjs-i18n

# yarn
yarn add @drawilet/nextjs-i18n

Getting started

Follow the i18n guide up to point 3, then come back here.

  1. Add the i18n option to your next.config.js.

    const i18n = require("./i18n.config");
    
    /** @type {import('next').NextConfig} */
    const nextConfig = {
      i18n: {
        locales: i18n.locales,
        defaultLocale: i18n.defaultLocale,
      },
    };
    
    module.exports = nextConfig;
  2. Add the I18nProvider to your _app.tsx (.jsx) file.

    import type { AppProps } from "next/app";
    import { useRouter } from "next/router";
    
    import { I18nProvider } from "@drawilet/nextjs-i18n";
    import resources from "../locales/data.json"; // OUTPUT_PATH
    
    export default function MyApp({ Component, pageProps }: AppProps) {
      const router = useRouter();
    
      return (
        <I18nProvider resources={resources} router={router}>
          <Component {...pageProps} />
        </I18nProvider>
      );
    }
  3. In the pages where you want to use i18n, import the useI18n hook.

    import { useI18n } from "@drawilet/nextjs-i18n";
    
    export const _i18n = {
      title: "Hello World",
    };
    
    const Page = () => {
      const i18n = useI18n();
    
      return (
        <div>
          <h1>{i18n("title")}</h1>
        </div>
      );
    };
    
    export default Page;

    For components

    import { useI18n } from "@drawilet/nextjs-i18n";
    export const _i18n = {};
    
    const Header: Component = () => {
      const i18n = useI18n("components", "/Layout/Header");
    
      return <header></header>;
    };
    export default Header;

Note

Remember to use the command npx i18n generate every time you update the texts to be translated.