I am using
tap:i18n for internationalization for quite a while, and it worked quite well. But now I am facing a weird behaviour which is driving me crazy. If I add more i18n keys to a language file for DE, they are just ignored and the package falls back to EN, even if other DE language keys can be retrieved from the very same JSON file. So I end up with a strange mix of language in my app. It started in one dialog, but now also other, newer dialogs are affected.
Strange thing is that this behaviour is indeterministic. For instance, the language shows up fine if Meteor just refreshes after the change. But as soon as I stop and restart the server, the language mix appears. It can also happen that some of the keys have been translated properly, while others don’t.
I debugged the package and found out that in the case that the keys are not translated, they are missing in the internal “resStore” for “de”. Other keys from the same JSON file are there, so only some keys are missing (but only in the DE translation, not in the EN base language). I double-checked the JSON, and also my linter does not complain about the syntax, so I think the JSON file itself is just fine. The English file has the very same structure, so I can just not understand why some keys are missing in the translation.
Did anybody else face this strange behaviour and may have an explanation for this - or is it just me who is affected?