The first step in vetting a new dependency for me is always documentation (not just taken at face value but also how well it corresponds to reality). The more c

The first step in vetting a new dependency for me is always documentation (not just taken at face value but also how well it corresponds to reality). The more complex the functionality and the larger the scope, the more it matters. First, since writing a library is a lot about design, and design is about communication, documentation provides many indirect but useful signals. Second, no project (whether dev-to-dev or dev-to-end-user) exists at a discrete point in time, and as every piece evolves documentation will be critical for making it manageable, especially if the project is not something done for hire.