1. Convert all source files to TypeScript
2. Polyfill too modern features

See also: https://foundryvtt.com/releases/11.307

The label of the add-button wraps to the next line, which results in it overlapping the word generator list. It should instead remain on the same line as the button icon and not wrap.

For easier navigation when one has many word generators set up, they should be groupable (and sub-groupable, of course!). Groups should be collapsible, so they take up far less vertical space.

Currently, CRUD operations have to be made through WordGeneratorApplication. This represents explicit data and UI changes, made with the same function. While this system is simple and effective, it is also difficult to maintain and bloats up the presentation code, when instead changing the data should be just as straight-forward as changing the data.

The UI should simply "react" to its underlying data changing. The UI shouldn't care who changed the data and neither should it care how. All it should care about is the fact that data changed, and then react to it with a re-render of the affected data. This would make the UI code much sleeker and easier to maintain.

This would allow to chain generators in a flexible way. For example, there could be a generator for first names, one for last names and one for full names, which combines the input of the previous two generators (in a set order, i. e. first name then last name).

For improved performance.

Hi.

I can't get it to work,

Custom spelling/sequencing strategies do not yet have a mechanism by which to provide localized hints.
For every setting they specify, they must be able to provide either a localization key or localized string.