Sourced from i18next-cli's changelog.
1.73.1
- fix(extract): the
<Trans>child error added for #246 now also fires for{table.name},{fn()},{`a ${b}`}and any other child expression the extractor cannot serialise, not only for bare identifiers like{name}. react-i18next inlines the value at runtime, while extraction silently produced an empty<1></1>placeholder, so the key never matched. The message suggests the{{name: table.name}}object form. It also no longer asks for avaluesprop: react-i18next reads the value from the{{name}}object child itself, so<Trans>See table {{name}}</Trans>works on its own. Extraction output is unchanged. Fixes #290.
938cfa0
1.73.1bc99139
fix(extract): error on <Trans> children like {table.name} that
won't match at...83988c9
fix github actions