i18next-parser | Parse your code to extract translation keys/values and manage your catalog files | Internationalization library

I'm trying to setup localisation for an existing app. I've gotten fairly far. But something is not quite right.

My setup is having multiple translation calls in the files like so: {attribute: 'stress', text: t('dass21::I found it hard to wind down')},

As you can see, I changed the namespace separator to be a double :: since I have a lot of medical specific sentences which are hard to think keys for, so the actual sentence is the key.

To export the translation into json translations files I use: i18next 'src/**/*.js' which works fine. It makes a folder for every language, and in that folder, for every namespace it makes a file. (Eg in this case, it will make a file dass21.json).

My configuration for the i18next-parser is: