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

ericvera · 2021-01-18T19:53:44Z

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 (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. (fix: t macro as function not extracting #846 and feat: extract multiple comments per translation ID #854) (cc @semoal and @Bertg in case they have any ideas)
.babelrc

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

The text was updated successfully, but these errors were encountered:

semoal · 2021-01-18T21:32:05Z

Hi Eric! Thanks for using Lingui
Are you using plain lingui extract or are you passing NODE_ENV=production

ericvera · 2021-01-18T21:40:44Z

Hi Eric! Thanks for using Lingui
Are you using plain lingui extract or are you passing NODE_ENV=production

I was using lingui extract with the --overwrite option, but also tried with without that option (same result). No NODE_ENV set. Also tried echo before the command to make sure it is not set.

semoal · 2021-01-18T22:04:07Z

#433 We have here a similar issue here, let me create a sample repo (or if you could provide us a sample repo for reproducing the issue, I could check in detail tomorrow) :)

semoal · 2021-01-18T22:05:24Z

https://codesandbox.io/s/nextjs-lingui-djzqm?file=/pages/index.tsx Here is a codesandbox that you could modify with your changes :)

ericvera · 2021-01-18T22:11:10Z

I just set the NODE_ENV=test and it seems to work. I was not setting NODE_ENV=production, but I guess that would be the default?

semoal · 2021-01-18T22:14:14Z

I just set the NODE_ENV=test and it seems to work. I was not setting NODE_ENV=production, but I guess that would be the default?

Probably in some process is setting up NODE_ENV=production, or the ci.. Dunno
Is not a directly issue with lingui, this is because lingui uses source code trough AST to explore what needs to extract, so if the code is generated via NODE_ENV=production babel applies other algorithm and brokes lingui.

Anyways I'll take a look to our internal babel generator if we can force this to be in NODE_ENV=development for example..

ericvera · 2021-01-18T22:21:00Z

Sounds good. For some more info...

I used yarn repro with the below package.json definition and it works. a.js just contains console.log(process.env.NODE_ENV) which prints out undefined.

"scripts": {
   "repro" : "cross-env NODE_ENV=development lingui extract && node a.js"
   ...
}

fhuszti · 2021-01-22T14:42:26Z

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?

semoal · 2021-01-25T08:54:20Z

Exactly, basically node_env=production applies changes to code that lingui can't interpret

semoal · 2021-01-27T15:48:43Z

I think i got a fix for this "issue", babel transform api allows to overwrite NODE_ENV variable internally, so probably won't be required to use nODE_ENV=development before lingui extract command.

@ericvera next tuesday we'll release a new version with this change introduced if you can tell us if this fixes the issue, would be amazing =)

ericvera · 2021-01-27T16:08:41Z

Happy to.

…

On Wed, Jan 27, 2021 at 9:49 AM Sergio Moreno ***@***.***> wrote: I think i got a fix for this "issue", babel transform api allows to overwrite NODE_ENV variable internally, so probably won't be required to use nODE_ENV=development before lingui extract command. @ericvera <https://github.com/ericvera> next tuesday we'll release a new version with this change introduced if you can tell us if this fixes the issue, would be amazing =) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#952 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUKOB3QL6EWUKJBIL64LKLS4AYW5ANCNFSM4WHYMYHA> .

semoal · 2021-02-02T09:42:32Z

@ericvera Released 3.5.0 give it a try plz

SleepWalker · 2021-02-02T10:26:48Z

The error is still there. It still does not work without NODE_ENV=development

semoal · 2021-02-02T10:28:29Z

Alright i'll take a deeper look, tough that forcing babel to use development was enough, but looks that NODE_ENV always has precedence.

If any of you has a reproduction repo where i can try will be super

SleepWalker · 2021-02-02T10:43:56Z

I'll try to debug it a little bit. Looks like the error happens somewhere after transformFileSync call. I have commented out that call and the error is still there.

That's because I'm using ts and therefore typescript extractor is executed 😅

SleepWalker · 2021-02-02T11:29:26Z

In my case the solution is to pass babelrc: false in the options here:

https://github.com/lingui/js-lingui/blob/main/packages/cli/src/api/extractors/typescript.ts#L50-L55

Here is babelrc from my project:

{
  "presets": [
    [
      "next/babel",
      {
        "preset-react": {
          "runtime": "automatic",
          "importSource": "@emotion/react"
        }
      }
    ]
  ],
  "plugins": ["@emotion/babel-plugin", "macros"]
}

The conflicting part is inside babel-plugin-transform-react-remove-prop-types which is enabled by next/babel in isProduction mode (detected from process.env:

https://github.com/vercel/next.js/blob/canary/packages/next/build/babel/preset.ts

If babel-plugin-transform-react-remove-prop-types is configured with { removeImport: true } (removes prop-types imports from code base), it will break the extract process. The error happens because of this line:

https://github.com/oliviertassinari/babel-plugin-transform-react-remove-prop-types/blob/d3a618a9c72be08485f5e20659c917b300cf7b74/src/index.js#L364

I don't know what scope.crawl does under the hood.

Looks like my issue is not due to the bug inside lingui 😅. I'll continue to use NODE_ENV=development

ericvera · 2021-02-02T18:17:08Z

@ericvera Released 3.5.0 give it a try plz

Same as @SleepWalker. Also still seeing the issue with the latest version.

armandabric · 2021-03-03T16:27:44Z

After upgrading from v3.2.3 to v3.6.0 I encounter the same error. Forcing the NODE_ENV to development fix the issue.

stale · 2021-05-02T18:09:33Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Manubi · 2021-08-03T07:55:03Z

Just wanted to let you know, I just switched to lingui and the fix was the node enviornment.
yarn run NODE_ENV=development lingui extract --clean && lingui compile

Anonymous-dev-v · 2021-10-06T17:17:38Z

The error is still there. Duplicate declaration "Trans"

gemcloud · 2021-12-28T19:05:58Z

I fixed the issue on my nextjs project on windows 10, windows 11!!!
Points are: 1 & 2
1. First of all you must install "npm i cross-env" on windows system (windows 10, 11).
2. You have to use "NODE_ENV=development" command
Notice: cross-env NODE_ENV=development! cross-env NODE_ENV=development!! cross-env NODE_ENV=development!!!
use below command on "package.json"

    "lang:extract": "cross-env NODE_ENV=development lingui extract --clean",

run "> yarn lang:extract" on console. each "messages.po" file created!
installed package version as below
"@lingui/react": "^3.13.0",
"@lingui/cli": "^3.13.0",
"@lingui/loader": "^3.13.0",
"@lingui/macro": "^3.13.0",

Hopeful help!

stale · 2022-05-25T22:27:44Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

armandabric · 2022-05-31T07:34:26Z

This is still a thing

2snEM6 · 2022-06-18T14:22:39Z

This is still happening to me in the latest version. I think this is not fixed

NitrousBGC · 2022-07-04T18:44:26Z

I fixed the issue on my nextjs project on windows 10, windows 11!!! Points are: 1 & 2 1. First of all you must install "npm i cross-env" on windows system (windows 10, 11). 2. You have to use "NODE_ENV=development" command Notice: cross-env NODE_ENV=development! cross-env NODE_ENV=development!! cross-env NODE_ENV=development!!! use below command on "package.json"
    "lang:extract": "cross-env NODE_ENV=development lingui extract --clean",
run "> yarn lang:extract" on console. each "messages.po" file created!

installed package version as below
"@lingui/react": "^3.13.0",
"@lingui/cli": "^3.13.0",
"@lingui/loader": "^3.13.0",
"@lingui/macro": "^3.13.0",

Hopeful help!

This did the trick for me ! Thank you!

mohanads · 2022-08-19T18:04:00Z

I ran into this and the NODE_ENV=development work-around didn't work.
However, removing the @babel/preset-env preset from my .babelrc fixed this issue.

Strnadj · 2022-08-30T07:02:17Z

I ran into this again, @babel/preset-env is not a part of my .babelrc... in case I remove it completely, lingui starts to complain.

ianchanning · 2022-09-09T18:05:43Z

I'm too using Next.js and I've been using the NODE_ENV=development fix for quite a while, but today for some reason or another I started getting the same errors:

Cannot process file /src/components/hooks/useNotifications.js: Duplicate declaration "Trans"
  1 | import React, { useEffect, useState, useContext, useRef } from 'react'
> 2 | import { Trans } from '@lingui/macro'
    |          ^^^^^

I was using lingui 3.12.1 but I updated to the current latest 3.14.0.

I noticed that without using NODE_ENV=development all files gave errors, but with using it about only 9 files gave errors. For these ones I replaced <Trans> macro with i18n from useLingui() and the t macro instead.

i18n._(t`...`)

These fixed my errors one by one.

athammer · 2022-09-13T05:25:12Z

Also using next.js.

I tried downgrading all the way to 3.0 with no luck. I'm currently on 3.14.0. I also had to use the t macro function sadly. I'll keep digging to see if I can find the route of the issue.

capaj · 2022-09-15T09:12:25Z

This lingui:extract": "NODE_ENV=development lingui extract should really get documented as all the people who use next.js will have to set this for the extraction to work properly.

athammer · 2022-09-21T19:46:41Z

Possible solution here? In the meantime the band aid solution still seems to use cross-env and set NODE_ENV=development .

Not sure what exactly the fix for the library is but hopefully this can point someone in the right direction to fix this. I'm guessing this is impacting pretty much everyone trying to use this library right now.

timofei-iatsenko · 2023-01-19T09:43:56Z

Looks like its still an issue. I reopen this and assign for myself.

timofei-iatsenko · 2023-02-14T14:36:27Z

Fixed in #1367 would be released as part of v4

semoal pushed a commit that referenced this issue Jan 27, 2021

fix: NODE_ENV=production crashes lingui extract #952

f368b35

semoal added next release 📦 Issues resolved in next release triage: accepted bug labels Jan 27, 2021

semoal removed the next release 📦 Issues resolved in next release label Feb 2, 2021

stale bot added the wontfix label May 2, 2021

stale bot closed this as completed May 9, 2021

RafaelVidaurre mentioned this issue May 20, 2021

Conflict with twin.macro running extract #1069

Closed

stale bot added the wontfix label May 25, 2022

stale bot closed this as completed Jun 10, 2022

tomquirk mentioned this issue Jul 17, 2022

Draft: NextJS jbx-protocol/juice-interface#1397

Merged

3 tasks

belaczek mentioned this issue Jan 19, 2023

Can't import typescript extractor after updat to 3.16.0 #1348

Closed

timofei-iatsenko reopened this Jan 19, 2023

timofei-iatsenko self-assigned this Jan 19, 2023

timofei-iatsenko added 📦 extractor 📦 cli 👩‍💻 assigned and removed bug wontfix labels Jan 19, 2023

This was referenced Jan 23, 2023

V4 Roadmap #1359

Closed

refactor(extractor/babel)!: sealed, non-fragile babel extractor options #1367

Merged

andrii-bodnar added v4 ⚫ Next.js labels Feb 1, 2023

andrii-bodnar added this to the v4 milestone Feb 13, 2023

timofei-iatsenko closed this as completed Feb 14, 2023

Martin005 linked a pull request Feb 14, 2023 that will close this issue

refactor(extractor/babel)!: sealed, non-fragile babel extractor options #1367

Merged

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

ericvera commented Jan 18, 2021

semoal commented Jan 18, 2021

ericvera commented Jan 18, 2021

semoal commented Jan 18, 2021

semoal commented Jan 18, 2021

ericvera commented Jan 18, 2021

semoal commented Jan 18, 2021

ericvera commented Jan 18, 2021

fhuszti commented Jan 22, 2021 •

edited

Loading

semoal commented Jan 25, 2021

semoal commented Jan 27, 2021

ericvera commented Jan 27, 2021 via email

semoal commented Feb 2, 2021

SleepWalker commented Feb 2, 2021

semoal commented Feb 2, 2021

SleepWalker commented Feb 2, 2021 •

edited

Loading

SleepWalker commented Feb 2, 2021

ericvera commented Feb 2, 2021

armandabric commented Mar 3, 2021

stale bot commented May 2, 2021

Manubi commented Aug 3, 2021

Anonymous-dev-v commented Oct 6, 2021 •

edited

Loading

gemcloud commented Dec 28, 2021

stale bot commented May 25, 2022

armandabric commented May 31, 2022

2snEM6 commented Jun 18, 2022

NitrousBGC commented Jul 4, 2022

mohanads commented Aug 19, 2022 •

edited

Loading

Strnadj commented Aug 30, 2022

ianchanning commented Sep 9, 2022

athammer commented Sep 13, 2022

capaj commented Sep 15, 2022

athammer commented Sep 21, 2022 •

edited

Loading

timofei-iatsenko commented Jan 19, 2023

timofei-iatsenko commented Feb 14, 2023

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

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

Comments

ericvera commented Jan 18, 2021

semoal commented Jan 18, 2021

ericvera commented Jan 18, 2021

semoal commented Jan 18, 2021

semoal commented Jan 18, 2021

ericvera commented Jan 18, 2021

semoal commented Jan 18, 2021

ericvera commented Jan 18, 2021

fhuszti commented Jan 22, 2021 • edited Loading

semoal commented Jan 25, 2021

semoal commented Jan 27, 2021

ericvera commented Jan 27, 2021 via email

semoal commented Feb 2, 2021

SleepWalker commented Feb 2, 2021

semoal commented Feb 2, 2021

SleepWalker commented Feb 2, 2021 • edited Loading

SleepWalker commented Feb 2, 2021

ericvera commented Feb 2, 2021

armandabric commented Mar 3, 2021

stale bot commented May 2, 2021

Manubi commented Aug 3, 2021

Anonymous-dev-v commented Oct 6, 2021 • edited Loading

gemcloud commented Dec 28, 2021

stale bot commented May 25, 2022

armandabric commented May 31, 2022

2snEM6 commented Jun 18, 2022

NitrousBGC commented Jul 4, 2022

mohanads commented Aug 19, 2022 • edited Loading

Strnadj commented Aug 30, 2022

ianchanning commented Sep 9, 2022

athammer commented Sep 13, 2022

capaj commented Sep 15, 2022

athammer commented Sep 21, 2022 • edited Loading

timofei-iatsenko commented Jan 19, 2023

timofei-iatsenko commented Feb 14, 2023

fhuszti commented Jan 22, 2021 •

edited

Loading

SleepWalker commented Feb 2, 2021 •

edited

Loading

Anonymous-dev-v commented Oct 6, 2021 •

edited

Loading

mohanads commented Aug 19, 2022 •

edited

Loading

athammer commented Sep 21, 2022 •

edited

Loading