Placeholder keys being displayed in production

[n-ce]

The translation key values for placeholders
show fine in development but in production, it shows as {keyName}.
More details at n-ce/ytify#253 (comment)

I am using @lingui/core in vite + typescript project.
Here is my src/locales/en.ts
Here is the lingui config:

"lingui": {
    "locales": [
      "en",
      "pl"
    ],
    "sourceLocale": "en",
    "catalogs": [
      {
        "path": "src/locales/{locale}",
        "include": [
          "src"
        ]
      }
    ]
  },

Here is the src/scripts/i18n.ts :

import(`../locales/${locale}.ts`)
  .then(({ messages }) => {

    i18n.loadAndActivate({ locale, messages });
    attributes.forEach(attributeHandler);

  });

[Dragonite24]

In that case, most likely, you are uploading translations only for the 'pl' language, skipping the stage of uploading the initial messages for 'en' in the production build.
You should use stripMessageField parameter in the @lingui/babel-plugin-lingui-macro/@lingui/swc-plugin plugins.

react({
    ...
    plugins: [
        ['@lingui/swc-plugin', { stripNonEssentialFields: false }]
    ]
})

[timofei-iatsenko]

I would not recommend using stripMessageField this is for exotic setups. Also that will not work without registering a message compiler.

[timofei-iatsenko]

This is by design. Lingui is dropping original message from the bundle in production build, and keep this message in development build.

That is made to save size of the bundle, because if user is switched on the "pl" language, if we would not drop original messages (en) user will effectively load two message bundles en + pl.

You need to make sure that you load catalog for all languages, including a source one (en) and ensure that catalogs are up-to-date and compiled.