Why We Added a Console Notice to i18next — and Why We Removed It

i18next turns 15 this year. It has almost 15 million weekly npm downloads, powers applications in every industry across the world, and is maintained by a small core team — the same people who founded Locize.

This is the story of a decision we made, what it cost, and why we reversed it.

The sustainability problem nobody talks about

Open source maintainers are expected to deliver production-grade software, respond to issues, fix security vulnerabilities, and keep pace with a fast-moving ecosystem — for free.

We've tried the standard approaches:

• GitHub Sponsors — the numbers were honest and we're grateful for every contributor, but they never came nearly close to funding even a minimal part of a single full-time engineer.
• README badges and funding links — almost no one reads them.
• NPM funding metadata — same story.

The reality is that i18next exists today because of Locize — our own managed localization product, built by the i18next core team to fund the library's continued development. Every security fix, every new feature, every improvement is made possible because Locize pays for the time to build it.

The problem: most i18next users don't know this. They use the library, file issues, request features, and have no idea how it stays maintained. We're not complaining — that's the nature of open source. But it does create a real tension.

What we decided to do

In v25.8.0, we introduced a single console.info line that appeared when i18next initialized:

🌐 i18next is made possible by our own product, Locize — consider powering your project with managed localization (AI, CDN, integrations): https://locize.com 💙

The reasoning was straightforward. console.info is a developer-facing channel. It doesn't affect your end users, it doesn't break builds, it doesn't affect performance. And it reaches the one audience we actually wanted to reach: the developers who choose which tools their teams use.

We provided an opt-out via showSupportNotice: false, and later added a globalThis kill-switch for PaaS and third-party dependency scenarios, and an I18NEXT_NO_SUPPORT_NOTICE (and later also a NODE_ENV=production) environment variable for CI/CD pipelines.

What happened next

The developer community responded — loudly, and with legitimate concerns.

The loudest complaints were about developer experience: the notice appearing multiple times in Next.js builds, flooding test logs, appearing inside design systems that consumers couldn't configure. We addressed most of these iteratively: improving the deduplication logic, adding the globalThis kill-switch, documenting the suppression options properly.

But the complaint that made us think hardest came from a PaaS provider who filed a detailed incident report. Their claim: the console notice may have caused Google Safe Browsing to block hundreds of customer sites.

We investigated carefully. Our honest technical assessment is that console.info output is not evaluated by Google Safe Browsing — GSB scans DOM content, not console output, and a link to locize.com in the console would have to affect our own platform and thousands of direct users if that were the mechanism. We still believe the actual cause was unrelated to the notice.

But here's what we couldn't dismiss: the reporter had a real production incident, affecting real customers, and the only change they made — adding the globalThis kill-switch at the infrastructure level via a Cloudflare worker — correlated with the block being lifted. We can argue about causation. We cannot argue about the operational burden that placed on them.

And we made a mistake in our response: we suggested a "bad actor on a subdomain" as the likely root cause. That was an assumption that didn't fit their specific setup — they don't host user-generated content — and we shouldn't have made it. We apologized for that.

What the data actually showed

We tracked where new Locize registrations came from, based on an optional "how did you hear about us?" field at signup. Over approximately two months and 226 responses:

14 people explicitly cited the console notice. The "i18next ecosystem" bucket likely includes more who saw it but described it differently. The notice drove some awareness. Not zero.

Why we're removing it

We're removing the notice in v26.0.0, and we want to be clear: this is not capitulation to pressure. We still believe the sustainability argument is correct. We still believe console.info is a legitimate channel. We still believe Locize is a fair way to fund open source.

We're removing it because when we weigh the costs and benefits honestly, the math has changed:

• The production friction — PaaS providers, library authors, third-party dependency scenarios — turned out to be more complex than we anticipated.
• The edge cases were real: CI pipelines, test logs, design systems, environments where suppression required infrastructure-level intervention.
• The community cost — issues filed, trust eroded, developers who saw it as a betrayal of open source principles — was higher than we expected.
• The conversion impact was real, and we're not convinced it would grow faster than the community cost it was accumulating.

v26.0.0 is a major release with several breaking changes and modernization work. Removing the notice cleanly — including the showSupportNotice option, the globalThis mechanism, and the env var — fits naturally into that release.

How you can actually support i18next

If this post resonated with you, here's what actually helps:

• Try Locize. It's built by the i18next team, integrates deeply with the ecosystem, and there's also a free plan to get started. If it fits your workflow, it directly funds the library you're using.
• Tell your team or decision-makers. If your company uses i18next in production, knowing that Locize funds its development is relevant information for anyone evaluating localization tooling.
• Mention it when it comes up. When someone asks about i18next in your community or on social media, it costs nothing to mention that Locize is how the library stays maintained.

We're not going anywhere. i18next will keep improving. The team is the same, the commitment is the same, and the library remains fully free and MIT-licensed.

We just learned something about how to talk about that — and we're adjusting accordingly.

— The i18next / Locize team