lingui extract to handle customized `Trans` component

[ippeiukai]

Is your feature request related to a problem? Please describe.

I have a customized Trans component.
npx -- lingui extract does not extract messages from their direct usage.

import { Trans } from '~i18n';

Macro usage works fine. runtimeConfigModule is configured as follows:

  runtimeConfigModule: {
    i18n: ['~i18n', 'i18n'],
    Trans: ['~i18n', 'Trans'],
  },

Describe proposed solution

lingui extract should support Trans component imported from other locations than hardcoded @lingui/react.

In addition to Trans from @lingui/react, lingui cli can pick up runtimeConfigModule.Trans or something similar from config file.

Describe alternatives you've considered

lingui extract could pick up any <Trans /> usage regardless of import path, like it does with i18n._(). It would break backward compatibility, however.

Additional context

@lingui/react is hardcoded here:

js-lingui/packages/babel-plugin-extract-messages/src/index.ts

Line 205 in 20d8478

.referencesImport("@lingui/react", "Trans")

Is runtimeConfigModule ignored by lingui-macro plugin when ran from lingui extract cli?

[RobertOstermann]

Any update on this? Is there a way to use a custom component or will the extract still not work? Would a custom extractor be required?

[timofei-iatsenko]

You can use macro.jsxPackage feature which recently landed here is doc: https://lingui.dev/ref/conf#macrojsxpackage

Here is a PR #2196

[ippeiukai]

@timofei-iatsenko Nice work!

Unfortunately, #2196 is for custom macros, and this issue is about non-macro usage of custom Trans implementation. Please reopen.