I went ahead and rebuilt the widget with Calcite components, and converted the widget to a functional component, rather than a class component since functional components are the more modern way of doing things. Either way would work just fine, and if you go back in the commit history, I made all of the UI changes before changing to a functional component, so you can still snag the class component version, with all of the UI upgrades.
I highly recommend sharing your widget using the standardization guidelines that I outline in this community post. Especially important is providing a license, as without one, it's difficult for organizations to really use your code in a serious manner. If you use GitHub, or another version control platform, that's even better, since you'll be able to accept suggestions from the community, and collaborate on the same project without juggling a bunch of different zip files.
