Not extracted messages get replaced with generated ids in the production build about js-lingui HOT 2 CLOSED

@krzkaczor hey, this is intentional design decision. During development (NODE_ENV==development) default messages included in bundle with a compiler. But for production build all non-essential properties and message compiler dropped. There is literally nothing to fallback to in production build.

The good solution would be to add an extract step just before running a production build in your CI pipeline.
I also recommend to use extract to template instead of normal extract.

Extract to template creating a "template" which you can then add to git ignore because it's an artifact produced from your code, such as sourcemaps. All cli tooling is aware of templates and will use it to fallback in case of message not found in original catalog.

I also recommend to use vite loader or webpack loader for catalogs to avoid explicit compilation step. So full solution would be:

• Use vite plugin or webpack loader and load your ".po" catalogs directly, example
• Add lingui extract-template just before build your application

  // package.json
      "build": "yarn extract-messages && next build",
      "extract-messages": "lingui extract-template",

• Use any TMS you want to manage and merge translations. The mimimal requirement is to support ICU message syntax and PO format. We use crowdin and it works fine.
• With lingui extract-template you load template file (for po-format it is template.pot) into TMS and download catalogs with translations (bunch of {lang}.po files). Even without TMS you can use POEditor desktop app to handle workflow with templates.

Note: As you see i also recommend to use Po format. I know that many developers in the beginning deciding to go with JSON because they think it would be easier to start with. But there are no advantages of json over PO files, because both of them you need to compile before use, but PO file will provide way better developer and translation experience than json.

from js-lingui.

@thekip Thank you for this detailed explanation. Helps a lot.

hey, this is intentional design decision. During development (NODE_ENV==development) default messages included in bundle with a compiler. But for production build all non-essential properties and message compiler dropped. There is literally nothing to fallback to in production build.

The good solution would be to add an extract step just before running a production build in your CI pipeline.
I also recommend to use extract to template instead of normal extract.

It would be great to mention this somewhere in the docs.

from js-lingui.