A JavaScript Utility... Library?

I complied a list of useful JavaScript stuff into a Github repository.

This repository includes code for functions like:

• Mix (Deep assign library that works with accessors).
• Getting translate values
• Getting keyboard focusable elements
• Normalizing button inconsistencies

And many others.

You can install the entire library with npm.

npm install @zellwk/javascript

Why this format?

I prefer publishing JavaScript stuff into one repository instead of splitting them into many small ones because:

1. It's easier for me to maintain – everything is in one place
2. It's easier for me to install – again, everything is in one place. No need to npm install a bajillion amount of libraries.

I was hesitant about releasing this library at first. It felt stupid. I thought nobody wouldn't use this collection anyway. I thought people prefer the current way where we install one small package each time with npm.

But Shawn Wang convinced me otherwise. He said it's okay as long as the library is treeshakable. Which makes sense. Shawn also told me Rich Harris had a similar thing called Yootils.

This idea gave me the permission to release this repository publicly, which is why I'm sharing this with you today. If you find this collection useful, please also give some credit to Shawn for expanding my thoughts.

---

Thanks for reading. This article was originally posted on my blog. Sign up for my newsletter if you want more articles to help you become a better frontend developer.