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

i18notion

v1.0.20

Published

Tool to integrate translations from Notion's workspace

Downloads

9

Readme

i18notion

Source i18next resources from your Notion workspace

Goal

i18notion act as a layer on top of i18next and allow you to effortlessly fetch your translations from a Notion block in your team's workspace and generate corresponding resource files

Installation

# With npm
npm install i18next react-i18next
npm install i18notion -D

# or yarn
yarn add i18next react-i18next
yarn add i18notion -D

Getting started

  1. Create a new Notion table containing your translations. First rows should contain your headers: one for the groups, one for the keys and one for each language you want to use. Here is an example:

Notion translation table

  1. Create a Notion internal integration following those instructions.

  2. Share the translation table page with your internal integration

  3. Retrieve yout internal integration API key and the block ID corresponding to the translation table. You can copy the block link and inspect the result to retrieve it. ie: In the following link https://www.notion.so/Translations-67bdf9435c38401583fde776581a0bf8#000aaa111bbb the block id would be 000aaa111bbb.

  4. Place those values in your .env file

NOTION_API_KEY=secret_n0t10n_4p1_k3y
NOTION_BLOCK_ID=000aaa111bbb
  1. Run 18notion specifying your resources directory path
  i18notion --resourcesDirPath="./src/features/i18n/resources"

Generated files content should look like this (ie: en.json)

{
  "general": {
    "title": "MyApp",
    "welcome": "Welcome on MyApp!"
  },
  "auth": {
    "login": "Login",
    "logout": "Logout"
  }
}
  1. Import the generated files in your i18next config
// ./src/features/i18n/init.ts

import i18next from 'i18next';
import { initReactI18next } from 'react-i18next';

import en from './resources/en.json';
import fr from './resources/fr.json';

export const initI18n = (): void => {
  i18next.use(initReactI18next).init({
    resources: {
      en: {
        translation: en,
      },
      fr: {
        translation: fr,
      },
    },
  });
};

Et voila! You're all set ✅