This is one thing I find a little bit frustrating with the tutorials of various JS tools. They fail to accurately describe a problem that they solve. Usually y

This is one thing I find a little bit frustrating with the tutorials of various JS tools. They fail to accurately describe a problem that they solve. Usually you just get a quick paragraph going on about what you can do with the tool, then a quick example of something you could have easily done without the tool, then straight into the full API documentation. And after I've read all that I'm still saying "Ok, that's kind of cool. But why would I add another dependency to my project when I can code your example up in clean, vanilla JS (or more often in these days, plain old React)". I'd love to start seeing tutorial documentation address this more. Having a basic example is great, but it shouldn't be the only example. You should follow it up with a more complex example that really captures the reason you built the tool in the first place.