refactor(i18n)!: adopt the shared i18n layer from stream-chat/i18n - #3271
Open
oliverlaz wants to merge 14 commits into
Open
refactor(i18n)!: adopt the shared i18n layer from stream-chat/i18n#3271oliverlaz wants to merge 14 commits into
oliverlaz wants to merge 14 commits into
Conversation
Replaces this SDK's own translation runtime with the shared one in
`stream-chat/i18n`, which the React Native SDK will adopt too. What stays here is
the part that is genuinely this package's: its generated key catalog, its bundled
data, and its notification translators.
Requires `stream-chat@10.0.0-rc.3` for the `stream-chat/i18n` subpath, so this
cannot merge before core publishes. The lockfile is deliberately untouched --
regenerate it once that release exists.
Deleted (~1,100 lines): `Streami18n.ts`, the formatter half of `utils.ts`,
`TranslationBuilder/TranslationBuilder.ts`, `externalStrings.ts`, and
`scripts/i18n-call-sites.mts`. `src/i18n/utils.ts` shrinks to a re-export so the
~15 internal import sites keep working, and the codegen script goes from 352 lines
across two files to ~40 lines of configuration.
- `types.ts` is now an instantiation of core's catalog-generic helpers, and
intersects `LanguageNameCatalog` and `RelativeTimeCatalog` -- keys core renders
and therefore owns. That also cut the two imports blocking the move:
`MessageContextValue` (a circular UI dependency) and `Moment` (a devDependency
type leaking into the published `.d.ts`).
- The 57 hand-maintained `language.*` names are gone; core derives them from the
same `TranslationLanguage` union the call site reads, so the key is checked.
`MessageTranslationIndicator` no longer needs `asDynamicKey` plus a string
comparison to detect a name that has no entry.
- `translatorsByNotificationType` is `Record<CoreNotificationType, Translator>`,
so a core identifier that gains no translator fails to compile. Two entries went
with it: `api:reply:search:failed` and `channel:jumpToFirstUnread:failed` were
copied between the two UI SDKs and neither is emitted by this one. Three
identifiers that *are* emitted and were unmapped now have translators.
- Notification translation dispatches on `notification.type` only. The
English-sentence table it fell back to is deleted -- prose matching could only
ever mask a missing translator entry.
- Poll field errors are keyed on `PollValidationError.code` rather than on the
English sentence the LLC produced, so a copy edit upstream can no longer
silently stop a translation from applying.
- `useChat` subscribes to the i18n `StateStore` instead of registering a single
callback that a second caller would clobber. It keeps its truthiness check on
`i18nInstance` -- an `instanceof` check would silently discard an instance from a
second copy of the package.
- The module-scope `Dayjs.extend` calls are gone from `TranslationContext`; core's
`defaultDateTimeParser` registers the plugins on first use, so the context
default still formats dates. This is the edit most likely to be reverted by
accident, and it fails silently -- as malformed dates, not a throw.
- `dayjs` and `i18next` move out of `dependencies`: core supplies them. Their
devDependency ranges now match core's exactly, because a second `dayjs` copy
breaks `instanceof` and, worse, means an integrator's `dayjs/locale/xx` import
lands on a different instance than the one formatting dates. That duplication
was real here until the ranges were aligned.
- The `sideEffects` entry for `./dist/i18n/Streami18n.js` is removed; vite never
emitted that path, so it matched nothing.
- New `catalogRenders` test, ported from the RN SDK: renders all 572 catalog
entries and every plural at four counts, asserting none surfaces as its own
dotted path or leaks a `{{ placeholder }}`. It is the only check that the
declared copy actually resolves -- the codegen proves a key *has* copy, not that
it comes out. Interpolation values are derived from each key's own copy so a
leftover placeholder means a real failure.
Two deliberate rendering changes, both confined to a key that specifies no format:
an unparseable or missing timestamp renders as empty rather than the literal text
`null`, and unformatted output is `2019-04-03T14:42:47+00:00` rather than `…Z`
because `.tz()` is now applied only when a timezone is actually configured.
BREAKING CHANGE: `Streami18n` is renamed `StreamI18n`, matching the shared class.
The old name is exported as a deprecated alias for one release cycle.
BREAKING CHANGE: `Streami18n.t` is a state-backed getter and can no longer be
assigned. Use `overrideTFunction(t)`, which publishes to the store `<Chat>`
subscribes to. `setLanguage()` now returns `void` for the same reason.
The v15 guide described the key rename and the dropped dictionaries but not the third breaking change in the same release: the runtime moved into `stream-chat`. An integrator following it would hit the class rename and two changed method shapes with nothing to explain them, and every example still used the deprecated name. Added a "shared runtime" section covering the `Streami18n` -> `StreamI18n` rename, `t` becoming read-only (use `overrideTFunction`), `setLanguage()` returning void, and dropping `i18next` / `dayjs` from your own dependencies -- with the one-command check for a duplicate `dayjs`, since a second copy means your `dayjs/locale/xx` import lands on a different instance than the one formatting dates and dates silently stay English. Documented the two rendering changes under Date and time, both confined to a `timestamp.*` key that specifies no format: a null or unparseable timestamp now renders as empty rather than the literal text `null`, and unformatted output carries a numeric offset rather than `Z` because `.tz()` is applied only when a timezone is configured. Also corrected a paragraph the move falsified: it said ~71 keys ship in `runtimeDefaults` including `language.*`. It is 15 now, and `language.*` plus the new `relativeTime.*` come from `stream-chat` -- still overridable, and still compile-checked, but no longer this package's data. Every claim in the new prose was checked against the built runtime rather than written from memory, which is how the "unparseable renders empty" half turned out to be false and got fixed in core instead of softened here.
…ted aliases
Core named the shared class `StreamI18n`, and this package re-exported `Streami18n` as a
`@deprecated` alias for one cycle. Both are reverted: core is `Streami18n`, matching the
name this SDK has shipped and documented for years, so integrators rename nothing and no
alias exists. The capital `I` was only ever cosmetic, and a deprecated alias in a breaking
release is cruft with a countdown attached.
`getTranslators()` went the same way. It was a `@deprecated` alias for `init()`, so it is
removed outright and the call sites here use `init()`, which returns the same state.
`init()` is the better name -- it initializes rather than gets -- and is idempotent, which
closes a re-entry window the old implementation left open.
The migration guide loses its "the class is renamed" section and gains one for
`getTranslators()`, which it had not documented.
BREAKING CHANGE: `i18n.getTranslators()` is removed. Use `i18n.init()`, which returns the
same `{ t, tDateTimeParser, language, initialized }`.
…en reference `size.yml` only ran on `master`, so no PR stacked onto `release-v15` measured the bundle -- leaving the i18n consolidation's central size claim, that moving the runtime into `stream-chat/i18n` shrinks the root bundle, unverified for the whole release. Also corrects a comment naming `i18next-cli` and the `aria/` key prefix, both removed in v15.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The only thing in this package that referenced i18next was a mock type in two
TranslationBuilder tests — `fromPartial<i18n>({ use: vi.fn() })`. Nothing in `src` imports
it at runtime or as a type.
`stream-chat/i18n` now re-exports the instance type as `I18nInstance`, which is where it
belongs: core's public API accepts an i18next instance, so a consumer implementing or mocking a
topic should not have to reach past `stream-chat` into its dependency and declare it
themselves. That was the same shape as the `moment-timezone` type leak.
`dayjs` and `moment-timezone` stay: three component tests build dates with dayjs, and the
bring-your-own-Moment parser test needs moment, which core no longer depends on at all. Both
are imported directly here, so both should be declared — not doing so is the bug that had
`yaml` resolving through lint-staged's tree in the core repo.
`Streami18n`, `getDateString` and `predefinedFormatters` live in `stream-chat/i18n` now — this package only re-exports them — so asserting their behaviour here duplicated core's suite in a second repo. Every assertion removed is covered on that side, and the six it did not cover were added there first (GetStream/stream-chat-js#1830). −1,154 lines. `utils.test.ts` goes entirely: all 570 lines were `getDateString` and `predefinedFormatters`. `Streami18n.test.ts` keeps the five describes that are genuinely about *this* package and drops the ten that were not: **Kept** — this SDK's catalog types and its `as const satisfies` completeness diff; the calendar keys that carry English words, which is an assertion about this catalog and its migration guide; the subclass merge behaviour (a caller's topic overriding the bundled `notification` one, and `runtimeDefaults` not being mutated as a shared module object); and the vitest timezone config. **Dropped** — default translator, prose resolution and `parseMissingKeyHandler`, registered and custom dictionaries, `registerTranslation`, `setLanguage`, timezone, formatters, the unregistered-language warning, and dates for an unregistered language. Core's G1/G2/G3 guarantees, `setLanguage`, `formatters` and `TranslationBuilder` suites assert all of it. Removing them made `moment-timezone` dead here, so it is dropped from devDependencies — core depends on no date library by name, its structural `DateTimeLike` covers both. `dayjs` stays: three component tests still build dates with it. Note the file opens with `/* eslint-disable */`, so the imports left dangling by the cut were invisible to lint and had to be found by hand. Worth removing that blanket disable separately. One correction folded in: renaming the i18next mock type last commit missed four `i18n['t']` casts in NotificationTranslationBuilder.test.ts. `tsconfig.test.json` is unenforced (~1200 pre-existing errors) so nothing flagged it; i18n test-type errors go 36 → 4, and the remaining four are pre-existing.
`MessageTranslationIndicator` compares the resolved name against the key again. The `language.*` keys being typed does not make them exhaustive at runtime: the union is generated when the SDK is built, while `message.i18n.language` is server data, so a language the translation API learns after this release has no entry and i18next echoes the key back -- rendering "Translated from language.sw" instead of falling back to the bare code. Covered by a new test that renders against a real `Streami18n`, since a mocked `t` would pass either way. `BundledKey` was declared privately in both `types.ts` and `Streami18n.ts`. It is now exported once and imported, so the exported `StreamTFunction` and the class instance's own `t` cannot disagree about the same call. Drops `src/i18n/__tests__/TranslationBuilder.test.ts`: `TranslationBuilder` is core's class re-exported from here, and eight of its nine cases duplicated core's own suite while asserting on private fields against a mocked i18next. The ninth -- removing a translator from the buffer before the topic exists -- moved to `stream-chat` rather than being lost.
`getTranslations()` and `getAvailableLanguages()` were public in v14 and are gone in v15, having left `stream-chat`'s surface entirely. Neither had a consumer here, but both were reachable by integrators, so the migration guide now shows the replacement for each -- render the key, and `registeredLanguages` respectively -- along with the six members that became private and the `ReadonlySet` change. The one test that used `getTranslations()` now asserts by rendering instead. It was reading the resource store to prove an app's own key had been written down; whether the key resolves is the thing worth asserting, and it holds without reaching past the public API.
Follows the `stream-chat` rename: `POLL_VALIDATION_CODE` and friends are now `POLL_COMPOSER_VALIDATION_CODE` / `PollComposerValidationCode`, matching the module they live in and the `PollComposer*` prefix already used by `PollComposerState` and `PollComposerOption`. Mechanical -- the identifier values are unchanged, so the `t()` keys these components map them to are untouched and no copy moves.
Review feedback: i18n did not belong in `useChat`, which was doing five unrelated jobs -- user-agent stamping, subsystem subscriptions, mutes, i18n and latest-message bookkeeping -- and only held the translators to hand them straight to a provider. It moves to `useStreami18n`, mirroring the hook `stream-chat-react-native` already has: adopt-or-create the instance, `init()` in an effect, subscribe to its store with a module-scope selector. Keeping the two SDKs the same shape here is the point -- React burying this inside `useChat` was exactly the divergence that moving the runtime into `stream-chat` set out to remove. `TranslationProvider` stays dumb, so `value` keeps working for tests and for anyone composing it by hand. Three things fall out of it: - The blanket `eslint-disable react-hooks/exhaustive-deps` is gone. `userLanguage` now tracks `client.user.language` reactively, so a user who connects *after* `<Chat>` mounts gets their language applied; it used to be captured once. The one disable left is narrow and documented: the instance memo must not depend on `client`, because re-running it would build a new `Streami18n` and discard every registered dictionary. - `if (!translators.t) return null` is deleted. `t` is seeded with the default translator and every store emission carries one, so it never fired -- a leftover from when `t` arrived asynchronously. - Instance recognition adopts RN's brand check. Truthiness was already cross-copy safe but accepted any truthy value, which then threw at render; the brand check warns and falls back instead. Five `Message` re-render assertions moved from `toHaveBeenCalledTimes(1)` to `toHaveBeenCalled()`. Both before and after this change mount settles at two renders -- measured -- but the old code delivered the post-`init()` translator after the test's await resolved and this delivers it during. Same work, one tick earlier. The assertions those tests exist for, the re-render on a prop change, are unchanged. BREAKING CHANGE: `useChat` no longer returns `translators`, and no longer accepts `defaultLanguage` or `i18nInstance` -- all three moved to `useStreami18n`. `<Chat>`'s props are unchanged; it wires both hooks internally. See "useChat no longer returns translators" in `ai-docs/i18n-v15-migration.md`.
oliverlaz
marked this pull request as ready for review
August 19, 2026 13:35
Three findings from an adversarial review pass. `window.navigator.language` is read after mount again, not during render. Extracting `useStreami18n` moved it into render, where there is no `window` on the server — and where a value differing from the server's is a hydration mismatch. `useChat` read it inside an effect; this keeps that timing, so the first client render agrees with the server's. `relativeCompactWeekRounding: ceil` is set on the two bundled keys that render relative dates. The formatter moved to `stream-chat`, whose default rounds *down*, and the two disagree visibly: `timestamp.ChannelMembersLastActive` and `timestamp.PollVote` had started reading "1w ago" at 8 days instead of "2w ago", and "3w ago" at 22-27 days where they used to fall through to a date. This restores the labels this SDK shipped. The lockfile is regenerated, and both examples move to the same `stream-chat` as the root. They pinned rc.2 while the root asked rc.3, so the lockfile legitimately carried two copies of the client — the split that makes `instanceof` fail and sends a registered dayjs locale to an instance nothing formats with. One copy now, and `yarn install --immutable` passes. Note the branch still does not build against a published core: no released version carries the `./i18n` subpath or the renamed poll API. The install gate is what this unblocks. Tests: week-label boundaries at 7/8/14/15/21/22/27 through the real bundled keys, and the browser-language read asserted to land after mount rather than during the first render. Not asserted through `renderToString`: `<Chat>` is not server-renderable today for an unrelated reason -- `useStateStore` calls `useSyncExternalStore` with no `getServerSnapshot`, so anything reading a `StateStore` throws on the server. A server-render test here would fail on that rather than on this hook. Recorded in both the hook and the test file so whoever fixes that knows to add one.
…State `DayjsLocaleConfig` was public on `release-v15` via `export * from './Streami18n'` and was dropped when the class became a subclass of core's: core exports it from `stream-chat/i18n`, but this package's re-export list omitted it. The localization guide instructs importing it from here to type `dayjsLocaleConfigForLanguage` and `registerTranslation`'s third argument, so an integrator following the guide got TS2305. `Streami18nState` is new, and it exists because `state` is public now. Subscribing to it wants a module-scope selector -- `useStateStore` takes the selector as a dependency of both its `useCallback` and its `useMemo`, so an inline one resubscribes on every render -- and that needs a nameable type. Core's default-parameterized `Streami18nState` will not do: it defaults the catalog to `AnyTranslationCatalog`, and `t` is contravariant in its options, so the concrete store is not assignable to it. `useStreami18n` had already declared exactly this alias privately; it now imports the exported one instead of keeping a second copy.
oliverlaz
added a commit
to GetStream/stream-chat-js
that referenced
this pull request
Aug 20, 2026
Moves the translation runtime shared by `stream-chat-react` and
`stream-chat-react-native` into this package as a new
**`stream-chat/i18n`** subpath, plus **`stream-chat/i18n/codegen`** for
the catalog generator. Both UI SDKs carried ~1,300 lines of
near-duplicate runtime that had drifted apart, each reverse-mapping this
package's English notification prose against its own hand-maintained
table of sentences.
**Breaking, and shipped together deliberately** — the first commit is
independently revertable if you'd rather split it:
- Notifications are keyed on `CORE_NOTIFICATION_TYPE` /
`CoreNotificationType`. `Notification.message` is now documented as a
developer-facing fallback whose wording is not contractual. Two
identifiers renamed (`api:message{s}:query:failed` → `messageJumpFailed`
/ `messageJumpToLatestFailed`).
- Poll-composer field errors become `{ code, message, metadata? }` keyed
on `POLL_VALIDATION_CODE`, instead of plain English strings.
- `engines.node` → `>=22.18.0` (the release that unflagged type
stripping, which the `.mts` build scripts need). Node 18/20 are no
longer tested — see the guide for what that means if you deploy the WS
client there.
- `i18next` and `dayjs` become direct dependencies. They stay out of the
root bundle; the subpath is what isolates them, and
`assertBundleBoundaries` fails the build if that ever regresses.
Also here: the generator moves out of `src/` to `codegen/i18n/` (it
reads the filesystem — not library source), ships ESM-only, and
`scripts/bundle.mjs` becomes `.mts` with a real typecheck gate.
**Docs:** `v9-to-v10-migration-guide-i18n.md` (new), plus a Node-floor
section in `-other.md`. Initiative record in `specs/i18n-to-core/`.
**Verified:** lint, all three `tsc` projects, 2,804 tests, and a
clean-install check of the packed tarball across all four export
conditions. The root bundle reaches neither `src/i18n/`, `i18next` nor
`dayjs` — machine-checked, not reviewed.
Consumer PRs, both blocked on this publishing as `10.0.0-rc.3`:
GetStream/stream-chat-react#3271 ·
GetStream/stream-chat-react-native#3777
oliverlaz
added a commit
to GetStream/stream-chat-js
that referenced
this pull request
Aug 20, 2026
## Why [Run 32373483292](https://github.com/GetStream/stream-chat-js/actions/runs/32373483292) succeeded and released nothing: ``` ℹ Found git tag v10.0.0-rc.4 associated with version 10.0.0-rc.4 on branch release-v10 ℹ Found 1 commits since last release ℹ Analyzing commit: feat(i18n)!: share the translation runtime as stream-chat/i18n (#1830) ℹ Analysis of 1 commits complete: no release ℹ There are no relevant changes, so no new version is released. ``` `@semantic-release/commit-analyzer` was configured with the **angular** preset, whose header pattern is: ```js /^(\w*)(?:\((.*)\))?: (.*)$/ ``` There is no slot for `!` between the scope and the colon, so a `feat(i18n)!:` header fails to match **entirely** — not just in its breaking marker. Parsing 40cf062 with each preset: | preset | `type` | `scope` | BREAKING notes | | --- | --- | --- | --- | | `angular` | `undefined` | `undefined` | 0 | | `conventionalcommits` | `feat` | `i18n` | 1 | With `type` and `notes` both empty nothing can match — not the custom `releaseRules`, and not the built-in defaults (`{breaking: true → major}`, `{type: 'feat' → minor}`). Those defaults were reachable: custom rules are tried first and the built-ins are the fallback. There is no `BREAKING CHANGE:` footer in the body either, which is the only other thing angular's parser reads. ## Three things this reconciles - `release-notes-generator` in this same config **already** uses `conventionalcommits`, so the two plugins disagreed. The notes would have rendered a breaking feature the analyzer never saw. - commitlint accepts the `!` form — the "Validate PR Title" check passed on that exact title — so we lint for a convention the release pipeline cannot act on. - The analyzer now understands both `!` and a `BREAKING CHANGE:` footer, rather than only the footer. ## Verification Replayed both presets through the real `analyzeCommits` over the last 400 commits on `master` and `release-v10`: ``` analyzed 400 commits verdict changes: 1 40cf062 none -> major feat(i18n)!: share the translation runtime as stream-chat/i18n (#1830) angular tally: {"none":165,"minor":103,"patch":127,"major":5} convcomm tally: {"none":164,"minor":103,"patch":127,"major":6} ``` Exactly one verdict changes; the other 399 are identical. Also confirmed the analyzer returns `major` when driven from `.releaserc.json` as written, so the preset resolves — `conventional-changelog-conventionalcommits` is already a devDependency. ## After this merges Re-running Release from `release-v10` still finds only 40cf062 since `v10.0.0-rc.4`, and will now cut **`10.0.0-rc.5`**. That is what unblocks [stream-chat-react#3271](GetStream/stream-chat-react#3271) and [stream-chat-react-native#3777](GetStream/stream-chat-react-native#3777), whose CI currently compiles against published rc.3 and so cannot see the `./i18n` subpath. `master` carries the identical angular config and the same latent bug, but no `!` commit has hit it yet. Worth the same one-line change there before one does.
github-actions Bot
pushed a commit
to GetStream/stream-chat-js
that referenced
this pull request
Aug 20, 2026
## [10.0.0-rc.5](v10.0.0-rc.4...v10.0.0-rc.5) (2026-08-20) ### ⚠ BREAKING CHANGES * **i18n:** share the translation runtime as stream-chat/i18n (#1830) ### Features * **i18n:** share the translation runtime as stream-chat/i18n ([#1830](#1830)) ([40cf062](40cf062)), closes [GetStream/stream-chat-react#3271](GetStream/stream-chat-react#3271) [GetStream/stream-chat-react-native#3777](GetStream/stream-chat-react-native#3777)
rc.5 is the first published core carrying the `stream-chat/i18n` subpath, so this is what makes the
branch installable and buildable against a real registry version rather than a locally packed
tarball. Bumped in the peer range, the dev dependency, and both example apps.
`i18next` now arrives transitively from core, as intended -- this package declares neither it nor
`dayjs` any more. `dayjs` is deduped so the vite example's `^1.11.20` and core's `^1.11.13` resolve
to one 1.11.23, rather than two copies where a `dayjs/locale/de` side-effect import could land on
the instance core is not using.
Four type errors remain, all inherited from `release-v15` rather than introduced here --
`APIErrorResponse`, `EventAPIResponse` (x2) and `channel.sendImage`, none of which core v10 exports
any more. Measured against `release-v15` with rc.5 installed: it has 8 errors and 45 failing tests,
this branch has 4 and 43. The difference is the poll-composer validation errors, which this branch
already adapted to `{ code, message }`.
Brings in the new upload API (#3272), the web counterpart of the React Native SDK's #3778. That clears the last four type errors on this branch, all of which it had inherited rather than caused: core v10 no longer exports `APIErrorResponse` or `EventAPIResponse`, and `channel.sendImage` is gone. Conflict resolution: four `stream-chat` version strings, `release-v15` at `10.0.0-rc.4` against this branch's `10.0.0-rc.5`. Kept rc.5 -- it is the first published core carrying the `stream-chat/i18n` subpath, so rc.4 would not resolve the subpath this branch imports. `yarn.lock` regenerated rather than hand-merged; `moment` and `moment-timezone` leave the tree with the bump, and `dayjs` is deduped to a single 1.11.23. Gates now clean for the first time on this branch: `tsc -p tsconfig.lib.json` 0 errors (was 4), 233 suites / 2729 tests passing (was 43 failing), lint 0, build 0.
oliverlaz
had a problem deploying
to
Vite Example Public (Preview)
August 20, 2026 14:54 — with 
GitHub Actions
Failure
oliverlaz
had a problem deploying
to
Vite Example Development (Preview)
August 20, 2026 14:54 — with
GitHub Actions
Error
|
Size Change: -13.7 kB (-1.63%) Total Size: 825 kB 📦 View Changed
ℹ️ View Unchanged
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## release-v15 #3271 +/- ##
==============================================
Coverage ? 84.13%
==============================================
Files ? 525
Lines ? 15640
Branches ? 5011
==============================================
Hits ? 13159
Misses ? 2481
Partials ? 0 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adopts the shared i18n layer from
stream-chat/i18n, deleting ~1,100 lines of runtime this package no longer needs to own:Streami18n, the formatter/date half ofi18n/utils.ts,TranslationBuilder/TranslationBuilder.ts,externalStrings.ts, and most of the codegen script (249 lines → ~40, over the generator core now ships).What stays here is what is genuinely this SDK's: the generated key catalog,
runtimeDefaults, and the notification translation topic.Behaviour changes
Record<CoreNotificationType, Translator>, so a new identifier instream-chatis a compile error until mapped. Dead rows for identifiers this SDK never emits are gone; three previously-unmapped core identifiers now translate instead of rendering untranslated English.language.*entries move to core, generated fromTranslationLanguage, soMessageTranslationIndicatordrops itsasDynamicKey+ string-compare miss detection.StateStore.setLanguage()returnsvoid;getTranslators()is nowinit(). No deprecated aliases —Streami18nkeeps its name, so integrator code is unchanged there.ai-docs/i18n-v15-migration.md.i18next/dayjs/moment-timezonefromdependencies— core supplies the first two, and the third's type leak into the published.d.tsis replaced by core's structuralDateTimeLike.Also adds a
catalogRenderstest (this package had no equivalent of RN's regression net) and putsrelease-v15insize.yml's branch filter, which was only running onmaster.Verified against a locally packed core: 2,829 tests,
validate-esm,validate-cjs, lint. Adopting the shared layer surfaced seven real defects in it, all fixed in the core PR with regression tests.stream-chat@10.0.0-rc.3(GetStream/stream-chat-js#1830). The lockfile is deliberately untouched and must be regenerated once that publishes — until thenyarn install --immutablefails, hence draft.Pre-existing and not from this PR:
yarn build'stscstep fails on 3 imports (APIErrorResponse,EventAPIResponse) removed from core after rc.2. Needs fixing when this package bumps its core range.