HyperTS has been developed and used by many active community members. Everyone is more than welcomed to make the project better and more accessible to more users. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
We are proud of this project and have been working to make it great since day one. We believe you will love it and we need your help and everything about HyperTS you have in your mind pushes this project forward.
Join Us!
The single most important contribution that you can make is to report bugs and make feature requests. The development work on HyperTS is largely driven by these, so please make your voice heard!
Here are some issue templates we recommend while you report bugs or suggest features.
- Bug Issue
- Feature Request
- Other Issues
Ideally, you can attach some code in your issue to reproduce the bug.
Code contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
- You are working against the latest source on the master branch.
- You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
- You open an issue to discuss any significant work - we would hate for your time to be wasted.
To send us a pull request, please:
- Fork the repository.
- Modify the source
- Ensure local tests pass.
- Commit to your fork using clear commit messages.
- Send us a pull request.