Bug: Transloco-keys-manager 6.1.0 and jsverse transloco 7.5.1 don't work together

[Nijaz-Zaljevic]

Is there an existing issue for this?

• I have searched the existing issues

Is this a regression?

No

Current behavior

i18n:find fails after the update of the both packages.
Message

Warning: command "transloco-keys-manager find --project test-app -e --config /" exited with non-zero status code

Expected behavior

Shouldn't fail with the message. It works with Transloco-keys-manager 6.0.0

Please provide a link to a minimal reproduction of the bug

Not needed

Transloco Config

No response

Debug Logs

No response

Please provide the environment you discovered this bug in

Transloco: 7.5.1
Transloco Keys Manager: 6.1.0
Angular: 19.8.14
Node: 
Package Manager: 20.3.0
OS:

Additional context

No response

I would like to make a pull request for this bug

No

[shaharkazaz]

@Nijaz-Zaljevic Can you run it with debug and share more information?

[Nijaz-Zaljevic]

Sure, but first, is there a newer way to activate the debug logs?
"i18n-find": {
"executor": "nx:run-commands",
"options": {
"commands": [
{
"command": "DEBUG=* transloco-keys-manager find --project -e --config /"
}
]
}
},

This doesn't work, it leads to this:

'DEBUG' is not recognized as an internal or external command,

[shaharkazaz]

@Nijaz-Zaljevic And what if you run it directly and not via nx? Debug with tkm should work.

[Nijaz-Zaljevic]

@shaharkazaz it doesn't matter if I run it directly inside the terminal or if I replace the i18n:find command and then via npm run, I always receive 'DEBUG' is not recognized as an internal or external command.

E.g.

"i18n:find": "DEBUG=tkm:* transloco-keys-manager find  --project project -e --config /",


"i18n:find": "DEBUG=tkm:config transloco-keys-manager find  --project project -e --config /",

[shaharkazaz]

Any chance you are on windows? The Debug is an env var

[Nijaz-Zaljevic]

Okay, I got it. I would say the logs for the versions 6.0.0 and 6.1.0 are equal with one difference and that is the part with the missing keys. This comes only with 6.1.0, which then leads to a failure of the command.

[shaharkazaz]

@Nijaz-Zaljevic can you share those logs and a small reproduction? 🙂
Can you tell which keys are missing? Maybe I need to make some adaptations for angular v19

I need more information to help resolve this

[xDivisionByZerox]

I can confirm this bug. I was able to solve this issue by either reverting the @jsverse/transloco version to 7.5.0 OR the @jsverse/transloco-key-manager version to 6.0.0.

The debug logs for both versions are the same with except the last line listing the found keys.

With transloco@7.5.0 and transloco-key-manager@6.1.0:

33 keys were found in 92 files.

With transloco@7.5.1 and transloco-key-manager@6.1.0:

3 keys were found in 92 files.

What I noticed is that the 30 missing keys were all translated via the transloco pipe.

[shaharkazaz]

@xDivisionByZerox Thanks for the details! that's helpful

[xDivisionByZerox]

@shaharkazaz I've investigated this problem again after I had to redo my workspace setup at work today.
Interestingly, I don't run into any problems anymore. The find command correctly "finds" all keys, reports missing keys (which didn't work before since no keys where found at all) and also exists with the expected exit code (0 if no keys are missing, 1 if keys where found that are not present in translation files).

I sadly can't tell you exactly what changed. Since we are using pined dependencies, it shouldn't have been a problem with locale setups having slightly different dependencies installed. We upgraded to angular 19 meanwhile, maybe this has some impact?

That being said, this issue has been resolved (at least for me).

[shaharkazaz]

@xDivisionByZerox Thanks for the update! I was unable to find the root cause myself, everything seems to be working as expected

[emzet]

@shaharkazaz I think this can be related to this issue #215

[murieletrentini]

I've been working with @Nijaz-Zaljevic on the same project. The issue resolved itself, after upgrading to angular 19