Frontend: Cleanup i18next logs#8459
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
nabramow
reviewed
May 5, 2026
Contributor
📝 Release NotesThis PR does not need to be included in release notes. Reason: This PR is mainly a developer-experience cleanup for local frontend logs and fixes issues discovered during development, but it does not introduce a noticeable end-user feature, UX change, or significant user-facing bug fix in production. 🤖 Bot Debug InformationModel: |
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The console output from a local
yarn startis almost unusable because of the amount of i18next logging, which includes every loaded string. Unfortunatelyi18next, and especiallynext-i18nextdon't allow muting only that log level, so my only solution was monkey patchingconsole.log.This then exposed two warnings/errors that we had been missing:
en-CORPstrings were failing to load becausei18nextcanonicalized the locale toen-Corp.modstrings for non-English locales were erroring because they don't exist.The most verbose logs being filtered are:
Testing
Ran the frontend locally and reloaded /dashboard.
Before: over 8000 lines of junk, including:
After:
Web frontend checklist
For maintainers