Make input type handling more comprehensive.

Only keep lines that are testable.

Make tests more comprehensive.

Include coverage reporting on tests.

Include tests for duplicate values, as well as comprehensive date tests.

Reduce complexity in code by un-nesting ternary statements.

Correctly set fields when they are arrays.

Make readme more concise.

Indicate partial values can be passed in setFormValues().

Add files from pridepack.

Add logo, and some documentation.

Make error messages more user-friendly. Also remove magic constants
within functions.

Specify rootdir.

Include month and week input types.

Implement setFormValues for easy setting of fields.

Also migrated to pridepack because tsdx is already unmaintained.

Proofread README.

For republishing.

Exclude original source to minimize package size.

Ignore project files

Use separate file

Use correct logic.

Switch order in appearance of definitions.

The tests do not depend on separate files for loading templates. This is
for the layouts to be defined alongside the tests for easier updates.

The methods have been refactored and documented for ease of use of the
consumers.

Use correct description.

Add checkbox on sample form in README.

This adds the motivation on using the library, with the pitfalls on
using other form libraries.

Handle selects, as well as file uploads.

For republishing.

Set permissions to executable.

Use new URLs for publishing.

We have added a more meaningful code sample in the README file.

Also, the publishing will happen on multiple registries, just like
`@theoryofnekomata/react-musical-keyboard`

The tests are now fully unified with Jest and Cypress consuming the
same set of test files.

Jest, together with JSDOM, tests the behavior with static markup.

Cypress tests with dynamic markup.

Attempt to unify tests for Jest and Cypress.

Note on installation.

Include short details on using the library.

Both the JSDOM and the Cypress tests are organized.

This commit adds Cypress for testing the library against a real DOM.

Use custom JSDOM apart from Jest's built-in JSDOM instance because
we need to test different kinds of documents.

We will need to address problems with types, e.g. for `RadioNodeList`
because the runner could not find its declaration (for both our custom
and built-in JSDOM instances).

Add files from TSDX.