actualbudget/actual

[Maintenance] loot-core should not rely on i18next

Closed

#7,633 opened on Apr 26, 2026

View on GitHubContributor guide
 (2 comments) (1 reaction) (0 assignees)JavaScript (603 forks)batch import
good first issuehelp wantedmaintenance

Repository metrics

Stars
 (7,129 stars)
PR merge metrics
 (Avg merge 4d 15h) (165 merged PRs in 30d)

Description

The loot-core package should not reply on i18next. All user-facing translations should live in desktop-client package.

The objective here is to perform some refactors to remove usage of i18next from loot-core and then also remove this dependency from package.json.

Doing this will make managing translations easier as they will be self-container to a single package instead of scattered all over.

Contributor guide

Research direction
Identify all usages of i18next in loot core and refactor by passing translations from desktop client. Then remove the i18next dependency from loot core's package.json.
Tech stack
javascript
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65