eslint-plugin-no-hardcoded-strings 🌐

![Version](https://www.npmjs.com/package/eslint-plugin-no-hardcoded-strings)

Forbid rendering hardcoded strings in the JSX tree to encourage proper internationalization.

This plugin helps enforce internationalization best practices by detecting and reporting hardcoded strings in your JSX components that should be translated.

Example

The following examples demonstrate how the plugin works:

``jsx // Default configuration (allowedFunctionNames: ["t"])

// Plain text in JSX

Hello world

 // ❌ throws warning/error (hardcoded string)
{t("hello.world")}
 // ✅ ok (uses translation function)
// String literals in expressions
{"Hello world"}
 // ❌ throws warning/error (hardcoded string)
// Function calls with hardcoded strings
{someFunc("Hello world")}
 // ❌ throws warning/error (hardcoded string in function call)
{t("hello.world")}
 // ✅ ok (uses allowed translation function)
// Variables with hardcoded strings
const message = "Hello world";
{message}
 // ❌ throws warning/error (variable resolves to hardcoded string)
const translatedMessage = t("hello.world");
{translatedMessage}
 // ✅ ok (variable uses translation function)

// Ignored strings (with ignoreStrings: ["OK"]) // ✅ ok (string is in the ignored list)`

`Installation`

Via npm:

`bash npm i eslint-plugin-no-hardcoded-strings --save-dev`

Via yarn:

`bash yarn add -D eslint-plugin-no-hardcoded-strings`

`Configuration / Usage`

Depending on how you configured your eslint instance, the following configuration might look a bit different.

For example using a json format would require the keys to be in quotes etc.

`javascript // .eslintrc.js

module.exports = { // ... plugins: [ "no-hardcoded-strings", // ... maybe other plugins here ... ], rules: { "no-hardcoded-strings": [ "warn", { allowedFunctionNames: ["t", "translate", "i18n"], ignoreStrings: ["OK", "Cancel"], ignorePatterns: [/^[0-9\s\-:]+$/], // Ignore dates, times, numbers }, ], // ... maybe other rules here ... }, };`

This configuration would make eslint throw warnings whenever a hardcoded string is found in JSX that isn't processed through one of the allowed translation functions (t, translate, or i18n), and isn't in the ignored list or matching the ignored patterns.

`Configuration Options`

| Option | Type | Default | Description | | ---------------------- | -------- | ------- | ---------------------------------------------------------------- | |allowedFunctionNames | string[] | ["t"]| List of function names that are allowed for internationalization | |ignoreStrings | string[] | []| List of specific strings to ignore | |ignorePatterns | RegExp[] | []` | List of regex patterns to ignore |

Use Cases

This plugin is particularly useful for:

1. Enforcing internationalization in applications that need to support multiple languages
2. Ensuring all user-visible text is properly translated
3. Preventing developers from accidentally adding hardcoded strings
4. Maintaining consistency in how translations are handled across a codebase