JIYIK CN >

Current Location:Home > Learning > WEB FRONT-END > React >

React solves the problem of Ref returning undefined or null

Author:JIYIK Last Updated:2025/03/15 Views:

refReact most commonly returns undefined or null when we try to access the current property before its corresponding DOM element is rendered . To solve this problem, you need to useEffectaccess it in a hook or when an event is triggered ref.

Let's look at the following code in App.js

import {useRef, useEffect} from 'react';

export default function App() {
  const ref = useRef();

  console.log(ref.current); // 👈️ undefined

  useEffect(() => {
    const el2 = ref.current;
    console.log(el2); // 👈️ 这里打印元素
  }, []);

  return (
    <div>
      <div ref={ref}>
        <h2>迹忆客(jiyik.com)</h2>
      </div>
    </div>
  );
}

The results of running the above code are as follows

React solves the problem of Ref returning undefined or null

useRef()The hook can be passed an initial value as an argument. The hook returns a mutable ref object whose .currentattributes are initialized to the passed argument.

We didn't pass an initial value to useRef, so its current property is set to undefined .

If we pass null to the hook, then its current property will be null if accessed immediately .

Note that we have to access the current property of the ref object to access the div element on which we set the ref attribute.

When we refpass the prop to an element, for example <div ref={myRef} />, React sets the property refof the object .currentto the corresponding DOM node.

We use useEffectthe hook because we want to make sure that the ref is set on the element and that the element has been rendered to the DOM.

refIf we try to access the current property of directly in the component , we'll get undefined because the ref hasn't been set yet and the div element hasn't been rendered yet.

refWe can also access the current properties of the event handler .

import {useRef, useEffect} from 'react';

export default function App() {
  const ref = useRef();

  console.log(ref.current); // 👈️ undefined

  useEffect(() => {
    const el2 = ref.current;
    console.log(el2); // 👈️ 这里打印元素 
  }, []);

  const handleClick = () => {
    console.log(ref.current); // 👈️ 这里打印元素
  };

  return (
    <div>
      <div ref={ref}>
        <h2>迹忆客(jiyik.com)</h2>
      </div>

      <button onClick={handleClick}>Click</button>
    </div>
  );
}

When the user clicks the button, the ref is already set and the corresponding element has been rendered to the DOM, so we can access it.

For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.

Article URL:

Related Articles

Fix Uncaught ReferenceError: useState is not defined in React

Publish Date:2025/03/15 Views:142 Category:React

When we use the useState hook in our code but forget to import it, it generates the error Uncaught ReferenceError: useState is not defined. To fix this error, you need to import the hook before using it import {useState} from react . // ?️

React error Uncaught ReferenceError: process is not defined solution

Publish Date:2025/03/15 Views:116 Category:React

To resolve the “Uncaught ReferenceError: process is not defined” error in React, open a terminal in the root directory of your project and update the version of the `react-scripts` package by running `npm install react-scripts@latest` and reinstal

React Error Property 'X' does not exist on type 'Readonly<{}>'

Publish Date:2025/03/15 Views:139 Category:React

The React.js error “Property does not exist on type 'Readonly'” occurs when we try to access the props or state of an untyped class component. To fix the error, you need to use generics on the React.Component class to type the props or state of th

Fix the value prop on input should not be null error in React

Publish Date:2025/03/15 Views:141 Category:React

The warning "value prop on input should not be null" is caused when we set the initial value of an input to null or override the initial value setting it to null, e.g. from an empty API response. Use a fallback value to solve this problem.

Property does not exist on type 'JSX.IntrinsicElements' error in React

Publish Date:2025/03/15 Views:188 Category:React

When the name of a component starts with a lowercase letter, an error "Property does not exist on type 'JSX.IntrinsicElements" will appear. To fix this error, you need to make sure you always start your component names with an uppercase letter, instal

Scan to Read All Tech Tutorials

Social Media
  • https://www.github.com/onmpw
  • qq:1244347461

Recommended

Tags

Scan the Code
Easier Access Tutorial