I've been using my own super minimal unit testing framework for all of my personal projects for about 2 years (https://gitlab.com/distilled/distilled/tree/devel

I've been using my own super minimal unit testing framework for all of my personal projects for about 2 years (https://gitlab.com/distilled/distilled/tree/develop https://gitlab.com/distilled/distilled/tree/develop). It's designed to be very flexible, and very, very fast to get up and running -- for new projects I want to be able to start writing unit tests within 30s to a minute after calling `npm init`. As far as I know I'm the only person who currently uses it, but it's saved me so much time that even if I'm the only person who ever uses it, it'll have been well worth the effort I spent writing it. I'm working on a similar project for documentation generation (https://gitlab.com/dormouse/dormouse/ https://gitlab.com/dormouse/dormouse/), and I expect that to be the same deal -- I'll probably be the only person who uses it, but I don't care because it'll pay for itself just from the time it saves me. Part of the advantage of having your own frameworks that you tightly control and understand is that they can be more specific to what you need. It's a tough balance -- I don't advise people to constantly reinvent the wheel, but occasionally existing wheels are really badly designed (looking at you esdoc), and in those cases it's often less work to reinvent the wheel than it is to use a misshapen wheel forever.