actualbudget/actual

[Maintenance] loot-core should not rely on i18next

Open

#7,633 创建于 2026年4月26日

在 GitHub 查看
 (2 评论) (1 反应) (0 负责人)JavaScript (7,129 star) (603 fork)batch import
good first issuehelp wantedmaintenance

描述

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.

贡献者指南

技术栈
javascriptnodejs
领域
backend
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
knowledge of loot core packagefamiliarity with i18next
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
65
研究方向
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.