cannot parse the keys from all my specified project files

[hippolyte42]

🐛 Bug Report

Can not manage to retrieve all my keys and write them in my output files, it is currently missing every keys called in my components/**/*.{ts,tsx}, the other keys are well retrieved as wanted

To Reproduce

my config file is set with input as below

// Paste your code here
input: "./!(node_modules)/**/*.{ts,tsx}",

Expected behavior

parse all my specified files and add the new found keys in my output: "public/locales/$LOCALE/$NAMESPACE.json" file.

Your Environment

• runtime version: node v14.17.4
• i18next version: 5.3.0
• os: Windows 10

[joepsyko]

I have a similar problem, after updating to version 5.x.x it doesn't extract translation correctly

[karellm]

@buyhighHippo Can you provide a reproduceable example?

[glekner]

@karellm we have the same issue in our repo https://github.com/kubevirt-ui/kubevirt-plugin
if you check https://github.com/kubevirt-ui/kubevirt-plugin/blob/main/locales/en/plugin__kubevirt-plugin.json
you will see only 216 keys, for some reason the parser does not parse files inside src/utils/**

we have a script for parsing: https://github.com/kubevirt-ui/kubevirt-plugin/blob/main/package.json#L12

can you please help?

[tradingstratagem]

I found the problem, I had this in my source code:
label: t(''),
After removing it, the parser works perfectly

[upalatucci]

I can confirm! Also in our repo https://github.com/kubevirt-ui/kubevirt-plugin

[alk-mandrianarijaona]

I have just checked our project, I also found a t(''), this must be the root cause. I will remove that. Thanks @tradingstratagem @upalatucci

[alk-sdavid]

Hi 👋 indeed empty keys are resetting the namespace catalog here:

i18next-parser/src/helpers.js

Lines 30 to 33 in e875d60

	if (!key) {
	target[entry.namespace] = {}
	return { target, duplicate, conflict }
	}

I'm not sure to understand the logic here 🤔 Is it really intended?
t('') can mess up all translations from a project, and there is another use case I found in our codebase:

i18n.t("some key: {{key}}", { key: someVar })

It extracts an empty key too. After removing all the empty keys, it seems to work just fine, but this behavior looks quite dangerous 😅 what do you think?

[karellm]

Thanks for finding the issue @alk-sdavid. I've pushed a patch as 6.4.0

[alk-sdavid]

thanks @karellm it seems to work as expected now 👍