Help & Support

Yes. You can sponsor Quiet on GitHub to unlock access to a sponsors-only discussion forum where you can get help directly from me, the maintainer, as well as other members of the community. I typically respond within 24 hours.

I will always do my best to help you and I typically reply within 24 hours. However, a sponsorship doesn't guarantee that I'll be able to fix your problem every time.

I prioritize bug fixes that affect sponsors first. I try to submit fixes quickly, but some bugs are tricky and require more time, research, etc. I will communicate my progress with you so you're always aware of what's happening.

The forums are located here. Please note that the page will appear as a 404 error unless you're an active sponsor!

Yes. You can cancel your sponsorship any time, but you will lose access to the sponsors-only benefits when the sponsorship period expires.

Bugs should be reported on GitHub. You do not need to be a sponsor to report a bug, but priority is given to sponsors. For best results, please include a minimal reproduction with your report.

Features can be requested on GitHub. You do not need to be a sponsor to request a feature. Please search before posting to prevent duplicate requests and use the 👍 reaction to vote.

I generally don't accept sponsorships for specific features. This lets me focus on what's best for the library.

Component tag names, e.g. <quiet-button>, cannot be changed without modifying the source code due to the way tags are referenced in code and styles. Attempting to change tag names, e.g. by extending the associated classes, will cause unexpected breakages and isn't a supported feature of the library.

While components are written as classes, they aren't designed to be subclassed. This is not supported and isn't an objective of the library. Instead, use composition when possible.

Because custom elements are registered globally, I don't recommend using Quiet in a micro frontend architecture unless you move it to the top of the stack. Avoid loading the library multiple times, as this will cause version conflicts and load more code than is necessary.