hookstate VS react-hook-form

Hookstate

Avoid using complex state structures to make it easier to manage and debug. There are multiple libraries to help manage complex state management such as Redux, Hookstate, etc.

Link: https://hookstate.js.org/

As you stumble on this post and article, do check out one library not mentioned in this list: hookstate. I'm a big fan, the API is very simple and it offers lots of extendability options.

Why don't you try out hook state

Lo stack tecnologico è abbastanza standard per il 2022: il core è Next.js (quindi React, 18), di store managemente se ne occupa Hookstate e per un po' di collante in più c'è l'event emitter / pubsub Mitt.

I have been using Hookstate, curiously aanbidt never mentioned in lists like this.

I've never understood why Hookstate (https://hookstate.js.org/) doesn't get more love. It's super-simple (no boilerplate), modern (hook-based), performant (works great for all size apps) and even works outside of components beautifully. It's somewhat similar to context, but more robust and feature-rich (because it's a true state management solution, which context really isn't meant to be). It's basically the only way I've done state in React for a couple of years now and I wouldn't trade it for the world.

If your data requirements aren't particularly mutating / don't mutate regularly then the newer context api would be your friend it essentially variable that is scoped to your react tree which components can subscribe to changes of, but it is important to know that: unfortunately the current useContext hook (and by extension the rest of the context api) doesn't have any means of specifically "choosing" / "selecting" a part of that context state which is where it falls behind redux etc... - even though they technically operate very very similarly - both redux and context api make use of "subscriptions" to track state updates, just that the context api was designed as a means of "dependency injection" whereas redux was designed for managing state across an entire application. Passing data through props is practically the same, as before the hooks api - avoid prop drilling etc... if you're simply looking at avoiding prop-drilling and just passing some stateful value to another component thats deeply nested then context is your friend - as for redux, I personally am further inclined to hookstate as I think their api is really strong.

React Hook Form is one of the most popular libraries for building forms in React apps with over 39k stars on GitHub. The library has no external dependencies according to Bundle Phobia.

Link: https://react-hook-form.com/

The idea here is to first define an array of field names for each provider. We'll also need a map with more detailed information about each field. This map will contain the field name, label, type, and validation options. We'll use this map to render the form fields and also to validate the form. Finally, we'll have a Form component that will render the form fields based on their type and handle the form submission. We'll use React Hook Form to handle the form state and validation.

Now we need to install React Hook Form because that is the package we are going to use for building our form. We also need to install the package for SendGrid. cd into the sendgrid-contact-form folder and then run this command to install the packages:

Imagine someone unknowingly unleashing heavy computation on a component without useMemo. That computation will run on every component re-render. Not only that, The dependency array in your hooks (useEffect, useMemo, useCallback) are also checked in each re-render. It's like a double whammy for performance pitfalls! I know that you can avoid this by some technique like what react-hook-form done, but remember thats an extra complexity.

But now, all those difficulties are gone since I found React Hook Form and zod.

This will greatly simplify the handling of AJAX forms in React - like for instance for a search form. But again, this may not be enough to get rid of third-party libraries like React Hook Form, which does much more than just handle form submission (validation, side effects, etc).

We could consider to do all these steps specifically for each data-set; of course this isn't an efficient approach due to the amount of repeated code involved. So what if we could abstract all this in a single management? A way to do this could be using a simple configuration in which we specify each aspect for each input (its type, validations required and so on). And we can do this thanks to the extreme flexibility provided by React Hook Form.