Migration guide from 3.x to 4.x
Backward incompatible changes
Minimal required versions are:
- TypeScript (if used on the project): 4.1
Extractor configuration changes
The big change in the v4 is in extractor internals. Now it is less fragile, and doesn't depend on the host project settings.
For most projects, it should work without extra configuration as long as it is a valid ES code.
extractorBabelOptions is not useful anymore, please delete it from your config.
module.exports = {
- extractorBabelOptions: { [...] }
}
Change in generated ICU messages for nested JSX Macros
We have made a small change in how Lingui generates ICU messages for nested JSX Macros. We have removed leading spaces from the texts in all cases.
The generated code from the following nested component:
<Plural
id="message.id"
one={
<Trans>
One hello
</Trans>
}
other={
<Trans>
Other hello
</Trans>
}
value={count}
/>
was changed as follows:
<Trans
id="message.id"
message={
- "{count, plural, one { One hello} other { Other hello}}"
+ "{count, plural, one {One hello} other {Other hello}}"
}
values={{
count: count
}}
/>
Flow Syntax supported in the Extractor with the flag
If your project uses Flow, you need to explicitly enable support in the extractor:
module.exports = {
extractorParserOptions: {
flow: true
}
}
@lingui/cli/api/extractors/typescript was deleted
Extractor supports TypeScript out of the box. Please delete it from your configuration file.
No need to have NODE_ENV=development before lingui-extract
If your extract command looks like:
NODE_ENV=development lingui-extract
Now you can safely change it to just:
lingui-extract
Public interface of ExtractorType was changed
declare type ExtractorType = {
match(filename: string): boolean
- extract(filename: string, targetDir: string, options?: any): void
+ extract(
+ filename: string,
+ code: string,
+ onMessageExtracted: (msg: ExtractedMessage) => void,
+ options?: ExtractorOptions
+ ): Promise<void> | void
}
Read more about custom extractor on the Advanced: Custom Extractor page.
Configuration migrations for deprecated options were deleted
Migration for the following older options:
localeDir,srcPathDirs,srcPathIgnorePatterns,fallbackLocale
were deleted from the source code. This should affect only users who are migrating from v2 to v4 directly.