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

@i18n-scanner-rs/main

v0.2.13

Published

A superfast i18next scanner tool written in Rust, based on Oxc

Readme

I18n scanner rs

CI

A superfast i18next scanner tool written in Rust, based on Oxc
The node.js API is implemented by NAPI

How it works

This will follow the below flows to collect all the I18n contents via passed entry file

  1. Analyze all file references from entry files
  2. Find all import statements are includes the list below:
    • import * from 'i18next'
    • import * from 'react-i18next'
    • or any you passed packages
  3. find out the variable linked to the import statement
  4. recursively analyze the variable's references
  5. collect the first parameter of i18n function call or bypass from another function wrapped by the i18n function

Usage

import { scan } from '@i18n-scanner-rs/main'

const payload = {
  tsconfigPath: './tsconfig.json',
  entryPaths: ['./src/index.ts'],
  externals: ['react-i18next'],
  extendI18NPackages: [],
}

const result = scan(payload)

console.log(result)

Debug parsing / syntax compatibility issues

If a file uses syntax that is not fully supported by the current parser version, run with debug logs to locate the problematic file quickly:

RUST_LOG=debug node your-script.js

The scanner will print parse diagnostics (including file paths) so you can identify and isolate unsupported syntax.

Type declarations

export interface Member {
  name: string
  type: I18nType
  ns?: string
}
export interface I18NPackage {
  packagePath: string
  members: Array<Member>
}

export const enum I18nType {
  Hook = 'Hook',
  TMethod = 'TMethod',
  TransComp = 'TransComp',
  TranslationComp = 'TranslationComp',
  HocWrapper = 'HocWrapper',
  ObjectMemberT = 'ObjectMemberT',
}
export interface Payload {
  tsconfigPath: string
  entryPaths: Array<string>
  externals: Array<string>
  extendI18NPackages?: Array<I18NPackage>
}

export declare function scan(payload: Payload): Record<string, Array<string>>

License

For a detailed explanation on how things work, checkout the Oxc and NAPI doc

Copyright (c) 2025-present, Idler.zhu