{"componentChunkName":"component---src-templates-docs-js","path":"/docs/hooks-reference.html","result":{"data":{"markdownRemark":{"html":"
\n
\n

These docs are old and won’t be updated. Go to react.dev for the new React docs.

\n

These new documentation pages teach modern React:

\n\n
\n
\n

Hooks are a new addition in React 16.8. They let you use state and other React features without writing a class.

\n

This page describes the APIs for the built-in Hooks in React.

\n

If you’re new to Hooks, you might want to check out the overview first. You may also find useful information in the frequently asked questions section.

\n\n

Basic Hooks

\n

useState

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useState.

\n
\n
\n
const [state, setState] = useState(initialState);
\n

Returns a stateful value, and a function to update it.

\n

During the initial render, the returned state (state) is the same as the value passed as the first argument (initialState).

\n

The setState function is used to update the state. It accepts a new state value and enqueues a re-render of the component.

\n
setState(newState);
\n

During subsequent re-renders, the first value returned by useState will always be the most recent state after applying updates.

\n
\n

Note

\n

React guarantees that setState function identity is stable and won’t change on re-renders. This is why it’s safe to omit from the useEffect or useCallback dependency list.

\n
\n

Functional updates

\n

If the new state is computed using the previous state, you can pass a function to setState. The function will receive the previous value, and return an updated value. Here’s an example of a counter component that uses both forms of setState:

\n
function Counter({initialCount}) {\n  const [count, setCount] = useState(initialCount);\n  return (\n    <>\n      Count: {count}\n      <button onClick={() => setCount(initialCount)}>Reset</button>\n      <button onClick={() => setCount(prevCount => prevCount - 1)}>-</button>\n      <button onClick={() => setCount(prevCount => prevCount + 1)}>+</button>\n    </>\n  );\n}
\n

The ”+” and ”-” buttons use the functional form, because the updated value is based on the previous value. But the “Reset” button uses the normal form, because it always sets the count back to the initial value.

\n

If your update function returns the exact same value as the current state, the subsequent rerender will be skipped completely.

\n
\n

Note

\n

Unlike the setState method found in class components, useState does not automatically merge update objects. You can replicate this behavior by combining the function updater form with object spread syntax:

\n
const [state, setState] = useState({});\nsetState(prevState => {\n  // Object.assign would also work\n  return {...prevState, ...updatedValues};\n});
\n

Another option is useReducer, which is more suited for managing state objects that contain multiple sub-values.

\n
\n

Lazy initial state

\n

The initialState argument is the state used during the initial render. In subsequent renders, it is disregarded. If the initial state is the result of an expensive computation, you may provide a function instead, which will be executed only on the initial render:

\n
const [state, setState] = useState(() => {\n  const initialState = someExpensiveComputation(props);\n  return initialState;\n});
\n

Bailing out of a state update

\n

If you update a State Hook to the same value as the current state, React will bail out without rendering the children or firing effects. (React uses the Object.is comparison algorithm.)

\n

Note that React may still need to render that specific component again before bailing out. That shouldn’t be a concern because React won’t unnecessarily go “deeper” into the tree. If you’re doing expensive calculations while rendering, you can optimize them with useMemo.

\n

Batching of state updates

\n

React may group several state updates into a single re-render to improve performance. Normally, this improves performance and shouldn’t affect your application’s behavior.

\n

Before React 18, only updates inside React event handlers were batched. Starting with React 18, batching is enabled for all updates by default. Note that React makes sure that updates from several different user-initiated events — for example, clicking a button twice — are always processed separately and do not get batched. This prevents logical mistakes.

\n

In the rare case that you need to force the DOM update to be applied synchronously, you may wrap it in flushSync. However, this can hurt performance so do this only where needed.

\n

useEffect

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useEffect.

\n
\n
\n
useEffect(didUpdate);
\n

Accepts a function that contains imperative, possibly effectful code.

\n

Mutations, subscriptions, timers, logging, and other side effects are not allowed inside the main body of a function component (referred to as React’s render phase). Doing so will lead to confusing bugs and inconsistencies in the UI.

\n

Instead, use useEffect. The function passed to useEffect will run after the render is committed to the screen. Think of effects as an escape hatch from React’s purely functional world into the imperative world.

\n

By default, effects run after every completed render, but you can choose to fire them only when certain values have changed.

\n

Cleaning up an effect

\n

Often, effects create resources that need to be cleaned up before the component leaves the screen, such as a subscription or timer ID. To do this, the function passed to useEffect may return a clean-up function. For example, to create a subscription:

\n
useEffect(() => {\n  const subscription = props.source.subscribe();\n  return () => {\n    // Clean up the subscription\n    subscription.unsubscribe();\n  };\n});
\n

The clean-up function runs before the component is removed from the UI to prevent memory leaks. Additionally, if a component renders multiple times (as they typically do), the previous effect is cleaned up before executing the next effect. In our example, this means a new subscription is created on every update. To avoid firing an effect on every update, refer to the next section.

\n

Timing of effects

\n

Unlike componentDidMount and componentDidUpdate, the function passed to useEffect fires after layout and paint, during a deferred event. This makes it suitable for the many common side effects, like setting up subscriptions and event handlers, because most types of work shouldn’t block the browser from updating the screen.

\n

However, not all effects can be deferred. For example, a DOM mutation that is visible to the user must fire synchronously before the next paint so that the user does not perceive a visual inconsistency. (The distinction is conceptually similar to passive versus active event listeners.) For these types of effects, React provides one additional Hook called useLayoutEffect. It has the same signature as useEffect, and only differs in when it is fired.

\n

Additionally, starting in React 18, the function passed to useEffect will fire synchronously before layout and paint when it’s the result of a discrete user input such as a click, or when it’s the result of an update wrapped in flushSync. This behavior allows the result of the effect to be observed by the event system, or by the caller of flushSync.

\n
\n

Note

\n

This only affects the timing of when the function passed to useEffect is called - updates scheduled inside these effects are still deferred. This is different than useLayoutEffect, which fires the function and processes the updates inside of it immediately.

\n
\n

Even in cases where useEffect is deferred until after the browser has painted, it’s guaranteed to fire before any new renders. React will always flush a previous render’s effects before starting a new update.

\n

Conditionally firing an effect

\n

The default behavior for effects is to fire the effect after every completed render. That way an effect is always recreated if one of its dependencies changes.

\n

However, this may be overkill in some cases, like the subscription example from the previous section. We don’t need to create a new subscription on every update, only if the source prop has changed.

\n

To implement this, pass a second argument to useEffect that is the array of values that the effect depends on. Our updated example now looks like this:

\n
useEffect(\n  () => {\n    const subscription = props.source.subscribe();\n    return () => {\n      subscription.unsubscribe();\n    };\n  },\n  [props.source],\n);
\n

Now the subscription will only be recreated when props.source changes.

\n
\n

Note

\n

If you use this optimization, make sure the array includes all values from the component scope (such as props and state) that change over time and that are used by the effect. Otherwise, your code will reference stale values from previous renders. Learn more about how to deal with functions and what to do when the array values change too often.

\n

If you want to run an effect and clean it up only once (on mount and unmount), you can pass an empty array ([]) as a second argument. This tells React that your effect doesn’t depend on any values from props or state, so it never needs to re-run. This isn’t handled as a special case — it follows directly from how the dependencies array always works.

\n

If you pass an empty array ([]), the props and state inside the effect will always have their initial values. While passing [] as the second argument is closer to the familiar componentDidMount and componentWillUnmount mental model, there are usually better solutions to avoid re-running effects too often. Also, don’t forget that React defers running useEffect until after the browser has painted, so doing extra work is less of a problem.

\n

We recommend using the exhaustive-deps rule as part of our eslint-plugin-react-hooks package. It warns when dependencies are specified incorrectly and suggests a fix.

\n
\n

The array of dependencies is not passed as arguments to the effect function. Conceptually, though, that’s what they represent: every value referenced inside the effect function should also appear in the dependencies array. In the future, a sufficiently advanced compiler could create this array automatically.

\n

useContext

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useContext.

\n
\n
\n
const value = useContext(MyContext);
\n

Accepts a context object (the value returned from React.createContext) and returns the current context value for that context. The current context value is determined by the value prop of the nearest <MyContext.Provider> above the calling component in the tree.

\n

When the nearest <MyContext.Provider> above the component updates, this Hook will trigger a rerender with the latest context value passed to that MyContext provider. Even if an ancestor uses React.memo or shouldComponentUpdate, a rerender will still happen starting at the component itself using useContext.

\n

Don’t forget that the argument to useContext must be the context object itself:

\n\n

A component calling useContext will always re-render when the context value changes. If re-rendering the component is expensive, you can optimize it by using memoization.

\n
\n

Tip

\n

If you’re familiar with the context API before Hooks, useContext(MyContext) is equivalent to static contextType = MyContext in a class, or to <MyContext.Consumer>.

\n

useContext(MyContext) only lets you read the context and subscribe to its changes. You still need a <MyContext.Provider> above in the tree to provide the value for this context.

\n
\n

Putting it together with Context.Provider

\n
const themes = {\n  light: {\n    foreground: \"#000000\",\n    background: \"#eeeeee\"\n  },\n  dark: {\n    foreground: \"#ffffff\",\n    background: \"#222222\"\n  }\n};\n\nconst ThemeContext = React.createContext(themes.light);\n\nfunction App() {\n  return (\n    <ThemeContext.Provider value={themes.dark}>\n      <Toolbar />\n    </ThemeContext.Provider>\n  );\n}\n\nfunction Toolbar(props) {\n  return (\n    <div>\n      <ThemedButton />\n    </div>\n  );\n}\n\nfunction ThemedButton() {\n  const theme = useContext(ThemeContext);  return (    <button style={{ background: theme.background, color: theme.foreground }}>      I am styled by theme context!    </button>  );\n}
\n

This example is modified for hooks from a previous example in the Context Advanced Guide, where you can find more information about when and how to use Context.

\n

Additional Hooks

\n

The following Hooks are either variants of the basic ones from the previous section, or only needed for specific edge cases. Don’t stress about learning them up front.

\n

useReducer

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useReducer.

\n
\n
\n
const [state, dispatch] = useReducer(reducer, initialArg, init);
\n

An alternative to useState. Accepts a reducer of type (state, action) => newState, and returns the current state paired with a dispatch method. (If you’re familiar with Redux, you already know how this works.)

\n

useReducer is usually preferable to useState when you have complex state logic that involves multiple sub-values or when the next state depends on the previous one. useReducer also lets you optimize performance for components that trigger deep updates because you can pass dispatch down instead of callbacks.

\n

Here’s the counter example from the useState section, rewritten to use a reducer:

\n
const initialState = {count: 0};\n\nfunction reducer(state, action) {\n  switch (action.type) {\n    case 'increment':\n      return {count: state.count + 1};\n    case 'decrement':\n      return {count: state.count - 1};\n    default:\n      throw new Error();\n  }\n}\n\nfunction Counter() {\n  const [state, dispatch] = useReducer(reducer, initialState);\n  return (\n    <>\n      Count: {state.count}\n      <button onClick={() => dispatch({type: 'decrement'})}>-</button>\n      <button onClick={() => dispatch({type: 'increment'})}>+</button>\n    </>\n  );\n}
\n
\n

Note

\n

React guarantees that dispatch function identity is stable and won’t change on re-renders. This is why it’s safe to omit from the useEffect or useCallback dependency list.

\n
\n

Specifying the initial state

\n

There are two different ways to initialize useReducer state. You may choose either one depending on the use case. The simplest way is to pass the initial state as a second argument:

\n
  const [state, dispatch] = useReducer(\n    reducer,\n    {count: initialCount}  );
\n
\n

Note

\n

React doesn’t use the state = initialState argument convention popularized by Redux. The initial value sometimes needs to depend on props and so is specified from the Hook call instead. If you feel strongly about this, you can call useReducer(reducer, undefined, reducer) to emulate the Redux behavior, but it’s not encouraged.

\n
\n

Lazy initialization

\n

You can also create the initial state lazily. To do this, you can pass an init function as the third argument. The initial state will be set to init(initialArg).

\n

It lets you extract the logic for calculating the initial state outside the reducer. This is also handy for resetting the state later in response to an action:

\n
function init(initialCount) {  return {count: initialCount};}\nfunction reducer(state, action) {\n  switch (action.type) {\n    case 'increment':\n      return {count: state.count + 1};\n    case 'decrement':\n      return {count: state.count - 1};\n    case 'reset':      return init(action.payload);    default:\n      throw new Error();\n  }\n}\n\nfunction Counter({initialCount}) {\n  const [state, dispatch] = useReducer(reducer, initialCount, init);  return (\n    <>\n      Count: {state.count}\n      <button\n        onClick={() => dispatch({type: 'reset', payload: initialCount})}>        Reset\n      </button>\n      <button onClick={() => dispatch({type: 'decrement'})}>-</button>\n      <button onClick={() => dispatch({type: 'increment'})}>+</button>\n    </>\n  );\n}
\n

Bailing out of a dispatch

\n

If you return the same value from a Reducer Hook as the current state, React will bail out without rendering the children or firing effects. (React uses the Object.is comparison algorithm.)

\n

Note that React may still need to render that specific component again before bailing out. That shouldn’t be a concern because React won’t unnecessarily go “deeper” into the tree. If you’re doing expensive calculations while rendering, you can optimize them with useMemo.

\n

useCallback

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useCallback.

\n
\n
\n
const memoizedCallback = useCallback(\n  () => {\n    doSomething(a, b);\n  },\n  [a, b],\n);
\n

Returns a memoized callback.

\n

Pass an inline callback and an array of dependencies. useCallback will return a memoized version of the callback that only changes if one of the dependencies has changed. This is useful when passing callbacks to optimized child components that rely on reference equality to prevent unnecessary renders (e.g. shouldComponentUpdate).

\n

useCallback(fn, deps) is equivalent to useMemo(() => fn, deps).

\n
\n

Note

\n

The array of dependencies is not passed as arguments to the callback. Conceptually, though, that’s what they represent: every value referenced inside the callback should also appear in the dependencies array. In the future, a sufficiently advanced compiler could create this array automatically.

\n

We recommend using the exhaustive-deps rule as part of our eslint-plugin-react-hooks package. It warns when dependencies are specified incorrectly and suggests a fix.

\n
\n

useMemo

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useMemo.

\n
\n
\n
const memoizedValue = useMemo(() => computeExpensiveValue(a, b), [a, b]);
\n

Returns a memoized value.

\n

Pass a “create” function and an array of dependencies. useMemo will only recompute the memoized value when one of the dependencies has changed. This optimization helps to avoid expensive calculations on every render.

\n

Remember that the function passed to useMemo runs during rendering. Don’t do anything there that you wouldn’t normally do while rendering. For example, side effects belong in useEffect, not useMemo.

\n

If no array is provided, a new value will be computed on every render.

\n

You may rely on useMemo as a performance optimization, not as a semantic guarantee. In the future, React may choose to “forget” some previously memoized values and recalculate them on next render, e.g. to free memory for offscreen components. Write your code so that it still works without useMemo — and then add it to optimize performance.

\n
\n

Note

\n

The array of dependencies is not passed as arguments to the function. Conceptually, though, that’s what they represent: every value referenced inside the function should also appear in the dependencies array. In the future, a sufficiently advanced compiler could create this array automatically.

\n

We recommend using the exhaustive-deps rule as part of our eslint-plugin-react-hooks package. It warns when dependencies are specified incorrectly and suggests a fix.

\n
\n

useRef

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useRef.

\n
\n
\n
const refContainer = useRef(initialValue);
\n

useRef returns a mutable ref object whose .current property is initialized to the passed argument (initialValue). The returned object will persist for the full lifetime of the component.

\n

A common use case is to access a child imperatively:

\n
function TextInputWithFocusButton() {\n  const inputEl = useRef(null);\n  const onButtonClick = () => {\n    // `current` points to the mounted text input element\n    inputEl.current.focus();\n  };\n  return (\n    <>\n      <input ref={inputEl} type=\"text\" />\n      <button onClick={onButtonClick}>Focus the input</button>\n    </>\n  );\n}
\n

Essentially, useRef is like a “box” that can hold a mutable value in its .current property.

\n

You might be familiar with refs primarily as a way to access the DOM. If you pass a ref object to React with <div ref={myRef} />, React will set its .current property to the corresponding DOM node whenever that node changes.

\n

However, useRef() is useful for more than the ref attribute. It’s handy for keeping any mutable value around similar to how you’d use instance fields in classes.

\n

This works because useRef() creates a plain JavaScript object. The only difference between useRef() and creating a {current: ...} object yourself is that useRef will give you the same ref object on every render.

\n

Keep in mind that useRef doesn’t notify you when its content changes. Mutating the .current property doesn’t cause a re-render. If you want to run some code when React attaches or detaches a ref to a DOM node, you may want to use a callback ref instead.

\n

useImperativeHandle

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useImperativeHandle.

\n
\n
\n
useImperativeHandle(ref, createHandle, [deps])
\n

useImperativeHandle customizes the instance value that is exposed to parent components when using ref. As always, imperative code using refs should be avoided in most cases. useImperativeHandle should be used with forwardRef:

\n
function FancyInput(props, ref) {\n  const inputRef = useRef();\n  useImperativeHandle(ref, () => ({\n    focus: () => {\n      inputRef.current.focus();\n    }\n  }));\n  return <input ref={inputRef} ... />;\n}\nFancyInput = forwardRef(FancyInput);
\n

In this example, a parent component that renders <FancyInput ref={inputRef} /> would be able to call inputRef.current.focus().

\n

useLayoutEffect

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useLayoutEffect.

\n
\n
\n

The signature is identical to useEffect, but it fires synchronously after all DOM mutations. Use this to read layout from the DOM and synchronously re-render. Updates scheduled inside useLayoutEffect will be flushed synchronously, before the browser has a chance to paint.

\n

Prefer the standard useEffect when possible to avoid blocking visual updates.

\n
\n

Tip

\n

If you’re migrating code from a class component, note useLayoutEffect fires in the same phase as componentDidMount and componentDidUpdate. However, we recommend starting with useEffect first and only trying useLayoutEffect if that causes a problem.

\n

If you use server rendering, keep in mind that neither useLayoutEffect nor useEffect can run until the JavaScript is downloaded. This is why React warns when a server-rendered component contains useLayoutEffect. To fix this, either move that logic to useEffect (if it isn’t necessary for the first render), or delay showing that component until after the client renders (if the HTML looks broken until useLayoutEffect runs).

\n

To exclude a component that needs layout effects from the server-rendered HTML, render it conditionally with showChild && <Child /> and defer showing it with useEffect(() => { setShowChild(true); }, []). This way, the UI doesn’t appear broken before hydration.

\n
\n

useDebugValue

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useDebugValue.

\n
\n
\n
useDebugValue(value)
\n

useDebugValue can be used to display a label for custom hooks in React DevTools.

\n

For example, consider the useFriendStatus custom Hook described in “Building Your Own Hooks”:

\n
function useFriendStatus(friendID) {\n  const [isOnline, setIsOnline] = useState(null);\n\n  // ...\n\n  // Show a label in DevTools next to this Hook  // e.g. \"FriendStatus: Online\"  useDebugValue(isOnline ? 'Online' : 'Offline');\n  return isOnline;\n}
\n
\n

Tip

\n

We don’t recommend adding debug values to every custom Hook. It’s most valuable for custom Hooks that are part of shared libraries.

\n
\n

Defer formatting debug values

\n

In some cases formatting a value for display might be an expensive operation. It’s also unnecessary unless a Hook is actually inspected.

\n

For this reason useDebugValue accepts a formatting function as an optional second parameter. This function is only called if the Hooks are inspected. It receives the debug value as a parameter and should return a formatted display value.

\n

For example a custom Hook that returned a Date value could avoid calling the toDateString function unnecessarily by passing the following formatter:

\n
useDebugValue(date, date => date.toDateString());
\n

useDeferredValue

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useDeferredValue.

\n
\n
\n
const deferredValue = useDeferredValue(value);
\n

useDeferredValue accepts a value and returns a new copy of the value that will defer to more urgent updates. If the current render is the result of an urgent update, like user input, React will return the previous value and then render the new value after the urgent render has completed.

\n

This hook is similar to user-space hooks which use debouncing or throttling to defer updates. The benefits to using useDeferredValue is that React will work on the update as soon as other work finishes (instead of waiting for an arbitrary amount of time), and like startTransition, deferred values can suspend without triggering an unexpected fallback for existing content.

\n

Memoizing deferred children

\n

useDeferredValue only defers the value that you pass to it. If you want to prevent a child component from re-rendering during an urgent update, you must also memoize that component with React.memo or React.useMemo:

\n
function Typeahead() {\n  const query = useSearchQuery('');\n  const deferredQuery = useDeferredValue(query);\n\n  // Memoizing tells React to only re-render when deferredQuery changes,\n  // not when query changes.\n  const suggestions = useMemo(() =>\n    <SearchSuggestions query={deferredQuery} />,\n    [deferredQuery]\n  );\n\n  return (\n    <>\n      <SearchInput query={query} />\n      <Suspense fallback=\"Loading results...\">\n        {suggestions}\n      </Suspense>\n    </>\n  );\n}
\n

Memoizing the children tells React that it only needs to re-render them when deferredQuery changes and not when query changes. This caveat is not unique to useDeferredValue, and it’s the same pattern you would use with similar hooks that use debouncing or throttling.

\n

useTransition

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useTransition.

\n
\n
\n
const [isPending, startTransition] = useTransition();
\n

Returns a stateful value for the pending state of the transition, and a function to start it.

\n

startTransition lets you mark updates in the provided callback as transitions:

\n
startTransition(() => {\n  setCount(count + 1);\n});
\n

isPending indicates when a transition is active to show a pending state:

\n
function App() {\n  const [isPending, startTransition] = useTransition();\n  const [count, setCount] = useState(0);\n  \n  function handleClick() {\n    startTransition(() => {\n      setCount(c => c + 1);\n    });\n  }\n\n  return (\n    <div>\n      {isPending && <Spinner />}\n      <button onClick={handleClick}>{count}</button>\n    </div>\n  );\n}
\n
\n

Note:

\n

Updates in a transition yield to more urgent updates such as clicks.

\n

Updates in a transition will not show a fallback for re-suspended content. This allows the user to continue interacting with the current content while rendering the update.

\n
\n

useId

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useId.

\n
\n
\n
const id = useId();
\n

useId is a hook for generating unique IDs that are stable across the server and client, while avoiding hydration mismatches.

\n
\n

Note

\n

useId is not for generating keys in a list. Keys should be generated from your data.

\n
\n

For a basic example, pass the id directly to the elements that need it:

\n
function Checkbox() {\n  const id = useId();\n  return (\n    <>\n      <label htmlFor={id}>Do you like React?</label>\n      <input id={id} type=\"checkbox\" name=\"react\"/>\n    </>\n  );\n};
\n

For multiple IDs in the same component, append a suffix using the same id:

\n
function NameFields() {\n  const id = useId();\n  return (\n    <div>\n      <label htmlFor={id + '-firstName'}>First Name</label>\n      <div>\n        <input id={id + '-firstName'} type=\"text\" />\n      </div>\n      <label htmlFor={id + '-lastName'}>Last Name</label>\n      <div>\n        <input id={id + '-lastName'} type=\"text\" />\n      </div>\n    </div>\n  );\n}
\n
\n

Note:

\n

useId generates a string that includes the : token. This helps ensure that the token is unique, but is not supported in CSS selectors or APIs like querySelectorAll.

\n

useId supports an identifierPrefix to prevent collisions in multi-root apps. To configure, see the options for hydrateRoot and ReactDOMServer.

\n
\n

Library Hooks

\n

The following Hooks are provided for library authors to integrate libraries deeply into the React model, and are not typically used in application code.

\n

useSyncExternalStore

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useSyncExternalStore.

\n
\n
\n
const state = useSyncExternalStore(subscribe, getSnapshot[, getServerSnapshot]);
\n

useSyncExternalStore is a hook recommended for reading and subscribing from external data sources in a way that’s compatible with concurrent rendering features like selective hydration and time slicing.

\n

This method returns the value of the store and accepts three arguments:

\n\n

The most basic example simply subscribes to the entire store:

\n
const state = useSyncExternalStore(store.subscribe, store.getSnapshot);
\n

However, you can also subscribe to a specific field:

\n
const selectedField = useSyncExternalStore(\n  store.subscribe,\n  () => store.getSnapshot().selectedField,\n);
\n

When server rendering, you must serialize the store value used on the server, and provide it to useSyncExternalStore. React will use this snapshot during hydration to prevent server mismatches:

\n
const selectedField = useSyncExternalStore(\n  store.subscribe,\n  () => store.getSnapshot().selectedField,\n  () => INITIAL_SERVER_SNAPSHOT.selectedField,\n);
\n
\n

Note:

\n

getSnapshot must return a cached value. If getSnapshot is called multiple times in a row, it must return the same exact value unless there was a store update in between.

\n

A shim is provided for supporting multiple React versions published as use-sync-external-store/shim. This shim will prefer useSyncExternalStore when available, and fallback to a user-space implementation when it’s not.

\n

As a convenience, we also provide a version of the API with automatic support for memoizing the result of getSnapshot published as use-sync-external-store/with-selector.

\n
\n

useInsertionEffect

\n
\n
\n

This content is out of date.

\n

Read the new React documentation for useInsertionEffect.

\n
\n
\n
useInsertionEffect(didUpdate);
\n

The signature is identical to useEffect, but it fires synchronously before all DOM mutations. Use this to inject styles into the DOM before reading layout in useLayoutEffect. Since this hook is limited in scope, this hook does not have access to refs and cannot schedule updates.

\n
\n

Note:

\n

useInsertionEffect should be limited to css-in-js library authors. Prefer useEffect or useLayoutEffect instead.

\n
","frontmatter":{"title":"API di Riferimento degli Hooks","next":"hooks-faq.html","prev":"hooks-custom.html"},"fields":{"path":"content/docs/hooks-reference.md","slug":"docs/hooks-reference.html"}}},"pageContext":{"slug":"docs/hooks-reference.html"}},"staticQueryHashes":[]}