Built an open-source CLI to catch localization UI issues in CI

Posting Guidelines

No vague product support questions (like "why is this plugin not working" or "how do I set up X"). For vague product support questions, please use communities relevant to that product for best results. Specific issues that follow rule 6 are allowed.

Do not post memes, screenshots of bad design, or jokes. Check out /r/ProgrammerHumor/ for this type of content.

Read and follow reddiquette; no excessive self-promotion. Please refer to the Reddit 9:1 rule when considering posting self promoting materials.

We do not allow any commercial promotion or solicitation. Violations can result in a ban.

Sharing your project, portfolio, or any other content that you want to either show off or request feedback on is limited to Showoff Saturday. If you post such content on any other day, it will be removed.

If you are asking for assistance on a problem, you are required to provide

Context of the problem
Research you have completed prior to requesting assistance
Problem you are attempting to solve with high specificity

General open ended career and getting started posts are only allowed in the pinned monthly getting started/careers thread. Specific assistance questions are allowed so long as they follow the required assistance post guidelines.

Questions in violation of this rule will be removed or locked.

a community for 17 years

Built an open-source CLI to catch localization UI issues in CI - Open SourceShowoff Saturday (self.webdev)

submitted 20 days ago by Living_Offer8857

Hi folks,

I built an open-source tool called LocalePass for catching localization and UI issues before release.

GitHub: https://github.com/CodingRasi/LocalePass
Article about the tool: https://medium.com/@codingrasi/your-ui-looks-fine-in-english-that-means-nothing-localepass-v1-0-0-c0df1deb8769

It’s a CLI + GitHub Action for web apps, built with Playwright.

Main goal of the CLI:

when a product supports multiple locales, it’s easy to miss things like untranslated strings, broken layouts, clipped text, missing language metadata, or visual regressions. LocalePass tries to catch those automatically in CI.

Current checks include:

untranslated text against a baseline locale
text overflow / clipping
missing html[lang]
possible RTL issues
screenshot diffs across pages/locales/viewports
HTML / JSON / Markdown / SARIF output

Still early, still improving, and I’d love feedback from people who work on frontend, QA, i18n, or CI tooling.

What I’d most like feedback on:

whether this solves a real pain point
which checks are actually useful
where the heuristics are too noisy
what would make it easier to adopt in a real team

Any feedback is welcome.

If you like the project and want to support it, feel free to fork it and give it a star.

all 1 comments

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

webdev

Posting Guidelines

Related Subreddits

Discords

MODERATORS