Thanks for wanting to help. Small, focused changes are the easiest to review.
Open an issue and pick a template. Say what you did, what you expected and what happened instead, plus your OS and browser/runtime version.
- Fork the repository and create a branch from the default branch.
- Keep one change per pull request, and write commit titles that say why the change is needed.
- Do not rewrite shared history; fix a mistake with a new commit.
- Update the README and
CHANGELOG.md(under Unreleased) when behaviour that users see changes.
npm ci && npm testBy contributing you agree that your work is released under this repository's LICENSE.