---
title: "Discussion on \"Stop shipping hard‑coded strings: Meet i18nGuard — an i18n linter for JS/TS (i18next, React‑Intl, Lingui)\" | Hashnode"
description: "Discussion on \"Stop shipping hard‑coded strings: Meet i18nGuard — an i18n linter for JS/TS (i18next, React‑Intl, Lingui)\". Internationalization (i18n) issues are sneaky. A single hard‑coded string slips into a PR, a key is missing in one locale, another key stays unused for months — and users get a half‑translated UI.\nWhat if your tooling could catch these problems autom..."
url: "https://hashnode.com/posts/stop-shipping-hardcoded-strings-meet-i18nguard-an-i18n-linter-for-jsts-i18next-reactintl-lingui/68d2543060731a7bc29128c7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Stop shipping hard‑coded strings: Meet i18nGuard — an i18n linter for JS/TS (i18next, React‑Intl, Lingui)](https://deuwi.hashnode.dev/stop-shipping-hardcoded-strings-meet-i18nguard-an-i18n-linter-for-jsts-i18next-reactintl-lingui?utm_source=hashnode&utm_medium=feed)

Internationalization (i18n) issues are sneaky. A single hard‑coded string slips into a PR, a key is missing in one locale, another key stays unused for months — and users get a half‑translated UI. What if your tooling could catch these problems autom...

Sep 23, 2025 · 4 min read · deuwi.hashnode.dev  
Read the article

-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#ts](https://hashnode.com/tag/ts)
-   [#i18n](https://hashnode.com/tag/i18n)

## Written by

[Deuwi](https://hashnode.com/@Deuwi)

@Deuwi

  
[View profile](https://hashnode.com/@Deuwi)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
