Allow picking the bundle to which all translations will be outputted

[ma2ciek]

📝 Provide a description of the new feature

Problem

Ref: ckeditor/ckeditor5-vue#134 - during the translation process, a couple of errors occur in the Vue framework. Fixing them requires customization to our default translation process and some of them don't work.

1st problem: When there is no JS asset an error happens.

2nd problem: For multiple JS assets translations are exported to separate files. This works well in the production but it doesn't work at all during the development where the webpack creates files on the fly without saving them locally, and, what's worse, the server only serves known static files - other files become unavailable.

Idea

For the 1st problem: Nothing should happen as such a customized build is intentional.

As the second "replace" strategy of providing localization doesn't work well for plural forms and was removed in the past, this idea should not be rather taken into consideration. 

IMO the most valuable and safe solution would depend on allowing specifying the bundle to which all translations will be added. We could also support a RegExp pattern for targetting files that were built with some hashes - e.g. /chunk-vendors/ will match dist/js/chunk-vendors.5ef56efa.js. Such an option can be named translationsOutputFile and should take a string/regexp/fn for easier usage. In case of no file matching a fn/RegExp an error should be thrown, while in case of no matching file using the string option a file with all translations should be created. The later will also enhance the usage options of CKEditorWebpackPlugin.

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.