Right, I forgot about that. The `package.json` idea could still work, we need to load one for each language, but should be that much to load and can be lay loaded when the user wants to manually change the language. An alternative is a JSON file with the label and name for each language, that since is not a JavaScript file it could live inside nls, right?