Just my personal opinion, but it's unlikely anyone will pay for this given the amount of free alternatives, and it's unlikely anyone will use it in OSS projects because there is a paid tier.
https://github.com/react-spring/react-spring
https://github.com/Popmotion/popmotion/tree/master/packages/...
The funny thing is that even doing a proper investigation of the different libraries will easily take you over an hour.
Like I said before, it's just my opinion, but I'd take a library with thousands of stars and a group of people maintaining it over something unknown and paid any day. If you think it's a good idea to pay for this, more power to you.
Is OP's library not trying to be dead simple?
I think hooks are cool, but this proliferation of two APIs when using/authoring libraries is concerning to me.
And I tried to design it so that it saves you and your team a lot more than an hour.
One reason for paying is to ensure that the library is maintained: too many people out there assume that labor is free.
I would not pay for anything that isn't open source, though, because I do not want to become fully dependent on something that might disappear.
Here's the one that I've been working on recently: https://github.com/ismailman/react-spho
My philosophy is different though that I want to make it absolutely dead simple to make UIs animate organically vs being a feature-filled animation library. I think React-SPHO is actually the easiest to use animation library for React available as most things you want to do "just work" and anybody reading the code using the library knows exactly what's going on without having to read any documentation so ramp-up for basic use cases is effectively instant.