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

next-mini18n

v0.1.4

Published

Simple Internationalization library

Downloads

3

Readme

next-mini18n

This has nothing to do with the package "mini18n" on npm.

A minimal, type-safe internationalization library for Next.js

Goals

  • Minimal wire transfer: Don't send all translations on each page load.
  • Modular: Add only the functionality you need.
  • Type-Safety: Use typescript for code completion when accessing translations and refactor with ease.
  • Bundle size: Keep the client side bundle small.
  • Framework integration: This is built for nextjs
  • Minimalism: Keep the API surface small.

Non-goals

  • Batteries included: This library is not intended to do much on its own.
  • Other Frameworks: This is meant for react and nextjs.
  • Cleverness: This is supposed to stay simple and predictable.

Usage

  • Define translations in separate files next to your components:
// i18n/en.ts
const en = {
    Hello: 'Hello',
    World: 'World',
}
export default en
  • Lazy-load the translation files
// pages/index.tsx
import mini18n from "next-mini18n"
// this is imported just for the typing
// and won't be included in the bundle
import en from "i18n/en"

const { Hello, World } = mini18n<typeof en>((locale) => import(`i18n/${locale}`))
  • Use them in your component:
export default function HomePage() {
    return <h3><Hello /> <World /></h3>
}

What's cool about this?

  • It uses next/dynamic under the hood and therefore causes no trouble with SSR.
  • It needs very little client side code
  • You get nice completions when writing components
  • You get type errors when removing or renaming translations that are used somewhere
  • Interpolations are just functions
  • Translations can be arbitrary react components

What's less cool about this

  • It uses next/dynamic under the hood and therefore loads translations lazily after the first render cycle.

Features

  • Simple Translations
const en = {
    Hello: "Hello World"
}
  • Interpolation
const en = {
    Greeting: (props: { name: string }) => `Hello, ${props.name}`
}
  • JSX
const en = {
    Greeting: (props: { name: string }) => <span>Hello, <b>{props.name}</b></span>
}
  • Render Prop support
<Hello>{(hello) => <span>In {locale} Hello means {hello}</span>}</Hello>

Examples

There's an example in the example-folder.