Intro to hooks

React Hooks is a fancy name for functions that let you hook into React state and lifecycle features in functional components. This was introduced with the React 16.8 update and has since become an essential component of any React application.

What are React Hooks?

Hooks, which were introduced with React 16.8, allowed functional components to maintain states and lifecycle features without the use of classes. Simply put, hooks are features that allow function components to "hook into" React state and lifecycle features.

Why We Need React Hooks?

Previously, if you wrote a function component and realized you needed to apply some state to it, all you had to do was convert it to a class.

However, with the new update, you can simply use a Hook within the function component, making the refactoring process much easier.

also, there are many advantages of using React hooks like:

Increased flexibility in reusing existing code.
When the functional component becomes complex, there is no need to refactor it into a class component.
You don't need to be concerned about this at all.
There will be no more method bindings.
Using hooks makes it easier to distinguish between logic and UI.

React Hook Types

It is possible to divide the built-in hooks into two sections, which are given below. React offers a few built-in hooks, such as

Basic Hooks

useState useEffect useContext

Additional Hooks

useReducer useMemo useCallback useImperativeHandle useDebugValue useRef useLayoutEffect

Rules of Hooks

It ain’t Fight Club, but we do have some rules to follow:

Hooks should only be called at the top level of your function. They should not be used in loops, conditionals, or nested functions.
Hooks should only be called from React function components or custom hooks. Don't call them from outside of a component (what good would that do?). Keeping all calls within components and custom hooks also makes your code easier to follow because all related logic is grouped together.
Hook names must begin with "use." similar to useState or useEffect (well, not those two, those are taken).

The React team created some ESLint rules to catch problematic usage of hooks (install from here), and the linter needs a way to identify “a hook.” Hence the naming prefix. Nothing magical going on there. The linter will be able to warn you if you violate rule 1 or 2, but only if you follow rule