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

@wads.dev/i18n-react-eslint-plugin

v0.0.1

Published

ESLint rules that prevent untranslated user-facing strings in JavaScript, TypeScript and JSX.

Readme

@wads.dev/i18n-react-eslint-plugin

ESLint rules for detecting untranslated, user-facing strings in JavaScript, TypeScript, and JSX, and for keeping i18n catalog imports deliberate.

Requirements

  • Node.js 18 or later
  • ESLint 9 with Flat Config (the supported configuration model).

Installation

npm install --save-dev @wads.dev/i18n-react-eslint-plugin eslint

ESLint 9 Flat Config

Use the bundled recommended configuration in eslint.config.js:

import i18nJsx from '@wads.dev/i18n-react-eslint-plugin';

export default [
  {
    files: ['src/**/*.{js,jsx,ts,tsx}'],
    ignores: ['src/**/i18n/**', 'src/**/*.test.*', 'src/**/*.spec.*'],
    ...i18nJsx.configs['flat/recommended'],
  },
];

The recommended config enables both rules. To configure them independently:

import i18nJsx from '@wads.dev/i18n-react-eslint-plugin';

export default [
  {
    files: ['src/**/*.{js,jsx,ts,tsx}'],
    plugins: { 'i18n-jsx': i18nJsx },
    rules: {
      'i18n-jsx/no-untranslated-string': 'error',
      'i18n-jsx/no-restricted-i18n-import': 'error',
    },
  },
];

Rules

i18n-jsx/no-untranslated-string

Reports likely user-facing, untranslated string literals in JSX, JSX attributes, object properties, and template literals. Import paths, object keys, data attributes, common technical attributes, known utility-class lists, and strings inside describe, it, and test calls are ignored.

Invalid:

const screen = <Button label="Continue">Create account</Button>;
const option = { label: 'São Paulo', value: 'sp' };

Valid:

const screen = <Button label={messages.continue}>{messages.createAccount}</Button>;
const layout = <View className="flex items-center justify-between" />;
const request = { id: 'payment-released', status: 'available' };

Options

All array options extend their built-in defaults; they do not replace them.

| Option | Type | Purpose | | --- | --- | --- | | ignoredAttributes | string[] | JSX attributes whose literal values are never reported. | | ignoredFunctions | string[] | Call names whose nested string literals are ignored. | | ignoredProperties | string[] | Object properties whose literal values are ignored. | | forcedAttributes | string[] | JSX attributes that are always treated as user-facing when they contain a non-empty literal. |

{
  'i18n-jsx/no-untranslated-string': ['error', {
    ignoredAttributes: ['analyticsName'],
    ignoredFunctions: ['storiesOf'],
    ignoredProperties: ['analyticsCategory'],
    forcedAttributes: ['emptyStateText'],
  }],
}

i18n-jsx/no-restricted-i18n-import

Restricts imports and re-exports only inside files directly under an i18n/ directory. It allows local ./base imports, packages named @wads.dev/i18n-*, and composition from another catalog with the same filename (for example, fr.ts importing another fr.ts). Other imports are reported.

Invalid (in src/feature/i18n/en.ts):

import ptBR from './ptBR';
export { default } from '../shared/messages';

Valid (in src/feature/i18n/en.ts):

import type Translation from './base';
import feature from '../another-feature/i18n/en';
import { createCatalog } from '@wads.dev/i18n-ts';

Options

| Option | Type | Purpose | | --- | --- | --- | | allowedImportPatterns | string[] | Regular-expression source strings for additional allowed module specifiers. |

{
  'i18n-jsx/no-restricted-i18n-import': ['error', {
    allowedImportPatterns: ['^@project/i18n-tools(?:/|$)'],
  }],
}

Development

npm ci
npm run ci
npm run verify:release

verify:release runs syntax validation, linting, tests, and npm pack --dry-run.