Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot process file /<path>.tsx: Duplicate declaration "Trans"

See original GitHub issue

Describe the bug When running lingui extract I get the error Duplicate declaration "Trans" (“t” seems to be OK).

To Reproduce

Cannot process file /<path>.tsx: Duplicate declaration "Trans"
  15 | // i18n
  16 | import { useI18N, Locale } from 'i18n';
> 17 | import { t, Trans } from '@lingui/macro';

Expected behavior No error on lingui extract

Additional context

Tried v3.4.0 and still had issues
CLI version v3.2.1 repros the issue
CLI version v3.1.0 does not repro the issue
@babel/core @7.12.10
Using Lingui in a NextJS project
Looked at the diff (https://github.com/lingui/js-lingui/compare/v3.1.0...v3.2.1) and there are two changes that jump out, but I don’t understand the code enough to troubleshoot part this point. (https://github.com/lingui/js-lingui/pull/846 and https://github.com/lingui/js-lingui/pull/854) (cc @semoal and @Bertg in case they have any ideas)
.babelrc

{
  "presets": ["next/babel"],
  "plugins": ["macros"],
  "env": {
    "test": {
      "plugins": ["dynamic-import-node"]
    }
  }
}

Issue Analytics

State:
Created 3 years ago
Reactions:13
Comments:35 (13 by maintainers)

Top GitHub Comments

10reactions

fhuszticommented, Jan 22, 2021

Thanks guys, changing "extract": "lingui extract" to "extract": "NODE_ENV=development lingui extract" fixed it on my fresh install with NextJS. If I understood correctly what is said here I can keep it like that and not worry about it because it doesn’t need to have NODE_ENV=production when building for prod?

9reactions

Anonymous-dev-vcommented, Oct 6, 2021

The error is still there. Duplicate declaration “Trans”