hooks VS haunted

I re-read relevant documentation many times and am very aware of what purity means. I guess what's throwing me off is that every hook library uses such implementation of usePrevious: * react-hookz * ahooks * rooks

ahooks

react-use * ⭐️ 29.6k / 🔽 958k ahooks * ⭐️ 9.1k / 🔽 74k awesome-react-hooks * ⭐️ 8.1k / 🔽 74k usehooks-ts * ⭐️ 1.6k / 🔽 44k react-recipes * ⭐️ 850 / 🔽 1.2k react-hanger * ⭐️ 1.8k / 🔽 3.3k

Document: https://ahooks.js.org​

ahooks 库里面有一个 useLockFn

Web component browser APIs aren't that many, and not that hard to grasp (if you don't know about them, have a look at Google's Learn HTML section and MDN's Web Components guide); but creating a web component actually requires taking care of many small things. This is where web component libraries come in very handy, freeing us of having to think about some of those things by taking care of them for us. Most of the things I'll mention here are handled one way of another by other libraries (GitHub's Catalyst, Haunted, Hybrids, Salesforce's LWC, Slim.JS, Ionic's Stencil) but I'll focus on Google's Lit and Microsoft's FAST here as they probably are the most used web component libraries out there (ok, I lied, Lit definitely is, FAST not that much, far behind Lit and Stencil; but Lit and FAST have many things in common, starting with the fact that they are just native web components, contrary to Stencil that compiles to a web component). Both Lit and FAST leverage TypeScript decorators to simplify the code even further so I'll use that in examples, even though they can also be used in pure JS (decorators are coming to JS soon BTW). I'll also leave the most apparent yet most complex aspect for the end.

Haunted on GitHub: github.com/matthewp/haunted

Atomico and Haunted, to add the useController hook which underlies useQuery and co.

** WCs don't have to be classes. See matthewp/haunted which uses hooks like React. But that library is not a mixin or wrapper around lit-element; it would replace lit-element. It does use lit-html though.

I think the distaste many folks have for web components stems from a simple misunderstanding. The APIs collectively know as "web components" weren't intended to replace your favorite framework. As with most things that become part of the standard, these are lower level APIs that will be supported for a long, long time. They were given to us with the hope that we'd build great tools around them, which we have with Stencil, lit-element, hybrids, Haunted, and so many more.