all-round-calculator VS calc_for_everything

Hello folks!! 👋🏻 Announcing publicly 📢 I've made an npm package named "all-round-calculator" and have published it on u/npmjs Check it out:- https://www.npmjs.com/package/all-round-calculator Source code:- https://github.com/Susmita-Dey/all-round-calculator Contributions are always welcomed. 😊

Lastly, I just had to push my contributions to my fork and create a pull request for the changes I made. As you may remember in my previous contributions to this repo, the owner has setup a template for all contributors. I followed the template and then sent in my request. After I created the request, I noticed something new. The repo owner has implemented continuous integration into contributions made to their repo. This was done to not only test my code for deployment to their website, but to detect and fix vulnerabilities in my contribution. I actually found this to be really interesting, this application they used for this is called GitGuardian, if you wanted to check it out. I think I should learn more about it, and see if it's something I would like to use in future products.

I found a repo called calculator for everything. The main goal of the repo is to have a calculator for every equation out there on one website, whether it's for computer science, math, chemistry, etc. I liked this idea and noticed that there wasn't a large amount of physics calculators. So I wanted to create a density calculator, since it's a commonly used formula. I also, noticed that the README wasn't updated to include any of the currently implemented physics calculators. So the issue that I made to the repo owner would create a density calculator for the repo and make the necessary updates to the README to mention the implemented physics calculators.