fnando/i18n-js

It's a small library to provide the I18n translations on the Javascript. It comes with Rails support.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 18th, 2026
Created on September 2nd, 2009
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 506
Total Stargazers: 3,809 (+0)
Total Subscribers: 48 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.5 hours
Mean response time: 102.3 days
90th percentile: 501.6 days
Tracked items: 8

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 78 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • community feedback required (1)
  • v4 (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

i18n-js is a JavaScript internationalization library that brings Rails I18n translations to the client side.

The library solves the problem of duplicating translation strings across server and client code. Rather than maintaining separate translation files for JavaScript, i18n-js exposes your existing Rails I18n translations to JavaScript, allowing you to reference the same translation keys from both backend and frontend code. The approach works by generating JavaScript files that contain your translation data, which can then be accessed through a simple API in your client-side code.

The tool suits Rails applications where you want to avoid translation duplication and keep your i18n configuration centralized. It is particularly valuable for projects that already use Rails I18n and want to extend those translations to JavaScript without managing a parallel translation system. If your application uses a different backend framework or does not rely on Rails I18n, this library's tight Rails integration may not be the best fit.

The project maintains steady engagement with its codebase, accepting pull requests that address reported issues and user-requested features. Development activity shows consistent responsiveness to community contributions, with maintainers reviewing and merging changes that improve the library's functionality and compatibility. The project remains actively maintained with attention to keeping the library functional across different Rails and JavaScript environments.