Valere 7485b3d71f Use a dedicated i18next instance instead of the global singleton ...

Element Call configured the global i18next singleton. When Element Call
runs embedded in a host application rather than as its own page, that
singleton belongs to the host, so configuring it would clobber the
host's translations.

Create Element Call's own instance in utils/i18n.ts, configure it in the
initializer, and pass it to components via <I18nextProvider>. Drop
.use(initReactI18next) from the initializer: it registers the instance
as react-i18next's global default, which is the global we are trying to
avoid. Tests and stories keep using it, so that they do not need to wrap
every render in a provider.

Two modules imported `t` directly from "i18next" and so were bound to
the global instance: utils/errors.ts now calls i18n.t() on the instance
(reached at call time, since i18next only assigns `t` during init), and
QrCode uses useTranslation() like every other component.

No functional change.

2026-09-01 18:30:05 +02:00

..

main.ts

fix tests dep optimization issues

2026-05-11 19:50:32 +02:00

manager.ts

move show footer logic to callViewModel

2026-04-10 18:27:24 +02:00

preview.tsx

Use a dedicated i18next instance instead of the global singleton

2026-09-01 18:30:05 +02:00