JIYIK CN >

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

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

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

When the name of a component starts with a lowercase letter, we’ll get the error “Property does not exist on type 'JSX.IntrinsicElements”. To fix this error, we’ll make sure to always start our component names with an uppercase letter, install React typings, and restart our development server.

The following is an example of how the error occurs.

// 名称以小写字母开头
function myComponent() {
  return <h1>Hello world</h1>;
}

function App() {
  return (
    <div>
      {/* ⛔️ Property does not exist on type 'JSX.IntrinsicElements'. */}
      <myComponent />
    </div>
  );
}

export default App;

The problem in the code example above is that myComponent starts with a lowercase letter.

To resolve this error, you need to make sure all component names start with an uppercase letter.

function MyComponent() {
  return <h1>Hello world</h1>;
}

function App() {
  return (
    <div>
      <MyComponent />
    </div>
  );
}

export default App;

React uses this naming convention to distinguish between built-in elements such as p, div, spanand custom components that we define.

If the error is not resolved, restart the IDE and the development server.

If this doesn't help, make sure you have the typings for react installed. Open a terminal in the root directory of your project (where your package.json file is) and run the following command.

# 使用 NPM
$ npm install --save-dev @types/react @types/react-dom

# ----------------------------------------------

# 使用 YARN
$ yarn add @types/react @types/react-dom --dev

If the error is not resolved, try deleting node_modulesthe and package-lock.json (not package.json) files, re-running npm installand restarting the IDE.

# 👇️ 删除 node_modules 和 package-lock.json
$ rm -rf node_modules
$ rm -f package-lock.json

# 👇️ 清除 npm 缓存
$ npm cache clean --force

$ npm install

If the error persists, make sure to restart your IDE and development server. VSCode often glitches and sometimes restarting can fix the problem.

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

要解决 React 中的“Uncaught ReferenceError: process is not defined” 错误,需要在项目的根目录中打开终端并通过运行 `npm install react-scripts@latest` 更新 `react-scripts` 包的版本,并在必要时重新安装

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

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

当我们尝试访问未键入的类组件的 props 或状态时,会发生 React.js 错误“Property does not exist on type 'Readonly '”。 要解决该错误,需要使用 React.Component 类上的泛型来输入该类的道具或状

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

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

当我们将输入的初始值设置为 null 或覆盖将其设置为 null 的初始值时,会导致警告“value prop on input should not be null”,例如 来自空的 API 响应。 使用后备值来解决这个问题。

React uses Router to get the current route

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

Use the `useLocation()` hook to get the current route through React Router, such as `const location = useLocation()`. The hook returns the current location object. For example, we can access the pathname as location.pathname.

Scan to Read All Tech Tutorials

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

Recommended

Tags

Scan the Code
Easier Access Tutorial