fix: support react native 0.79

[vonovak]

Description

This PR is to discuss compatibility for React Native 0.79, working around dual-package hazard that's happening since support for package exports was enabled by default in facebook/metro#1448.

The issue can be reproduced in #2231.

There are 3 kinds of fixes:

• (1) specify custom export entry for react-native (workaround in library)
• (2) specify custom resolveRequest in metro config (workaround in userland):

config.resolver.resolveRequest = (context, moduleImport, platform) => {
  switch (moduleImport) { 
    case '@lingui/react':
      return { type: 'sourceFile', filePath: require.resolve('@lingui/react') };

    default:
      return context.resolveRequest(context, moduleImport, platform);
  }
};

• (3) fix babel plugin transforms (@lingui/react/macro). The comment I got:

Probably, the import is getting replaced but dropping the source import loc, which Metro needs to map the dependency to the original import
The good news is that category of problem should go away when we move off the Babel ESM transform and we don’t need to rely on source mappings to determine the original import style.
For now the best fix for lingui-js would be to preserve the source loc when it replaces an import - which it definitely should be doing anyway.

it looks like path.insertAfter in addImport is what breaks Metro bundler

Types of changes

• Bugfix (non-breaking change which fixes an issue)

Fixes # (issue)

Checklist

• I have read the CONTRIBUTING and CODE_OF_CONDUCT docs
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
js-lingui	✅ Ready (Inspect)	Visit Preview	Apr 17, 2025 7:34am

[github-actions]

size-limit report 📦

Path	Size
packages/core/dist/index.mjs	2.91 KB (0%)
packages/detect-locale/dist/index.mjs	618 B (0%)
packages/react/dist/index.mjs	1.35 KB (0%)

[timofei-iatsenko]

the path is incorrect here.

[timofei-iatsenko]

Could it be solved from documentation perspective? How other packages used in react native world handle the issue?