We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing a new feature
- Becoming a maintainer
We use GitHub to host code, to track issues and feature requests, and to accept pull requests.
A pull request is the best way to propose a change to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main
- If you've added code that should be tested, add tests
- Manually update the
version
property in the rootpackage.json
, ensuring you follow semver conventions when choosing the new version - Do the same in the
package.json
for the package that you have updated inpackages
- Update the documentation if required
- Ensure PR validation passes
- Issue the pull request
By submitting a code change, you agree that your contribution will be licensed under this project's MIT License. Please contact the maintainers if this is a concern.
We use GitHub Issues to track bugs. Report a bug by opening a new issue.
Great bug reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific
- Give sample code if you can
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports and this helps us to make sure we can address and prioritise bugs as efficiently as possible.
We enforce a consistent coding style using linting rules. Please ensure that your code adheres to the project's linting rules and avoids lint ignores.