When to Say No to the Latest JS Framework

Before trying a new framework on paid work, I want to be able to name the problem it solves. Being interested in it is a perfectly good reason to experiment, but a weaker reason to ask a whole team to learn it.

A small prototype can answer a lot. Build one awkward interaction, change it, and see what the code looks like afterwards. If the existing tools still feel easier, there's no obligation to switch. I can enjoy learning something without moving the project onto it.