🌍 📖 A readable, automated, and optimized (2 kb) internationalization for JavaScript
C-Rank Grade: B (Solid) - 42/100
External PR Merge Rate: 67%
Response Time: 4d
First Timer Success: -
lingui/js-lingui has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lingui/js-lingui respond to incoming external pull requests in approximately 84.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 41.6 places lingui/js-lingui in the B tier.
The external contributor pull request merge rate for lingui/js-lingui is 66.7%, based on public PR activity from non-core contributors.
lingui/js-lingui currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
🌍 📖 A readable, automated, and optimized (2 kb) internationalization for JavaScript
Active maintainer team in lingui/js-lingui welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/lingui/js-lingui?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~55 hours (83% approval). Large PRs (>500 lines) take ~403 hours (30% approval). Keep your diff compact for rapid review.
Verifications I've searched existing issues and this hasn't been reported yet. I've checked the docs and this isn't expected behavior. I'm using the latest version of Lingui, and the problem still occurs. Description Hello! I found two related gaps in the catalog sorting code, both still present on main. orderByMessage was fixed to use a hardcoded collator in #1808 to stop catalogs from sorting differently depending on the machine's locale, but that fix was never applied to orderByMessageId. #2394 added support for passing a custom orderBy function, but seems like makeConfig.ts's jest-validate schema was never updated to allow it. exampleConfig.orderBy is still just "message" (a bare string), so validate(config, configValidation) rejects a function. The only way around these right now is by patching. Patches are small, so I am happy to open a PR if that lightens the load for the maintainers. 😄 Reproduction Link No response Reproduction Steps // lingui.config.ts import { defin
Page https://lingui.dev/ref/conf#pseudolocale Type of Issue Missing information Description I was looking through pseudolocales, and as I was testing the output with the extend option, and I was getting something akin to: [[ Ĥèłłó ]] Turns out that expand simply attaches a prefix before and after the message. It does not use more characters... For example, I was expecting something like: [[¶øœĤèèłłóïøäß]] But, I guess this is not how it works. It turns out there is a hidden option: extendCharacter https://github.com/MartinCerny-awin/pseudolocale/blob/25f56961a216c873c167afaa7369632557229a73/src/str.ts#L5-L14 Suggested Improvement Document all options that are defined here but in the linguijs repo: https://github.com/MartinCerny-awin/pseudolocale/blob/25f56961a216c873c167afaa7369632557229a73/src/str.ts#L5-L14 Or define your own set of options, agnostic to the pseudolocalization library, and you can pass through through adhoc according to the pseudolocaliz
Page https://lingui.dev/ref/conf#macrojsxplaceholderdefaults Type of Issue Missing information Description Context: #2631 (comment) The jsxPlaceholderDefaults configuration can define a placeholder for a tag so that <a> becomes <link> instead of <0> for example. This is can be interpreted as multiple <a> generating <link1>...<linkN> etc. However, this is not the case and instead we get an error stating there is a placeholder collision because 2 tags tried to take the name <link>. Suggested Improvement Although I would wish the tags incrementally use a counter for <link1>...<linkN>. The library owners preferred not to. Meaning that if I want to have incremental placeholders or whatever, then I should manually tag them. Fair. I think that's valid, but I think it should be explicitly documented as such rather than being only found out during extraction 😅 I can open a PR, likely later this week for this. Contribution I'd be willing to open a pull request for this.
https://github.com/lingui/js-lingui/tree/main/examples It would be better to create a separate pull request for each example project.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to lingui/js-lingui, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of lingui/js-lingui acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
lingui/js-lingui has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 41.6 places lingui/js-lingui in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lingui/js-lingui currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for lingui/js-lingui are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.