actualbudget/actual

[Maintenance] loot-core should not rely on i18next

Open

#7633 opened on Apr 26, 2026

View on GitHub
 (2 comments) (1 reaction) (0 assignees)JavaScript (7,129 stars) (603 forks)batch import
good first issuehelp wantedmaintenance

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

Tech stack
javascriptnodejs
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
knowledge of loot core packagefamiliarity with i18next
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Identify all files in the loot core package that import or use i18next. Refactor each usage to either remove the translation call if it's not user facing, or move the translation logic to the desktop client package. After all usages are removed, delete i18next from loot core's package.json dependencies. Ensure no functionality is broken by verifying that all user facing strings are still translated via desktop client.