Expected corresponding JSX closing tag error in React
React.js error “ Expected corresponding JSX closing tag ” appears when we forget to close a tag in the JSX code . To fix the error, use self-closing tags like <input />
and make sure the order of opening and closing tags in the JSX code is correct.
Here is an example that produces the above error
export default function App() {
// ⛔️ Expected corresponding JSX closing tag for <input>.
return (
<div>
<h1>Hello world</h1>
<input id="icon_prefix" type="text" class="validate">
</div>
)
}
The problem in our example is that we forgot to close the tag of the input element.
We can use self-closing tags to fix the error.
export default function App() {
return (
<div>
<h1>Hello world</h1>
<input id="icon_prefix" type="text" class="validate" />
</div>
);
}
We used a self-closing tag for the input element. So instead of using , which caused the error
<input>
, we used<input />
.
This error is also commonly caused by img elements. Make sure to always close our img tags as <img src="..." />
.
<br />
The same is true for the and <hr />
tags.
We always have to close the tag or use a self-closing tag, otherwise React expects us to pass the children prop to the component.
It can also cause errors when we open and close tags in an incorrect order.
export default function App() {
// ⛔️ Expected corresponding JSX closing tag for <input>.
return (
<div>
<h1>Hello world
<span>Hello 123</h1></span>
</div>
);
}
The problem in the code snippet above is that h1
the <div> tag opens, then span
the <div> element begins, and then h1
the <div> tag span
closes before the <div> element.
To fix the error in this case, we must first close span
the tag.
export default function App() {
return (
<div>
<h1>
Hello world
<span>Hello 123</span>
</h1>
</div>
);
}
Always use closing or self-closing tags because if React finds only an opening tag, then it expects us to children
pass the attribute to the element and then close 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.
Related Articles
How to avoid cross-origin (CORS) issues in React/Next.js
Publish Date:2025/03/17 Views:166 Category:NETWORK
-
In this article, we will introduce how to avoid cross-origin (CORS) issues in React/Next.js. Cross-origin resource sharing (CORS) is a protocol that defines how web requests should be handled when crossing different URLs.
React Tutorial - Transferring Props
Publish Date:2025/03/16 Views:185 Category:React
-
React transfers Props. Props are generated when components are encapsulated. Components expose some properties (Props) to the outside world to complete some functions.
React Tutorial: Props Anti-Pattern
Publish Date:2025/03/16 Views:183 Category:React
-
React's Props anti-pattern, using Props to generate state in getInitialState is an anti-pattern - Anti-Pattern.
React Tutorial - Props Validation
Publish Date:2025/03/16 Views:99 Category:React
-
Props validation is a very useful way to use components correctly. It can avoid many bugs and problems as your application becomes more and more complex. In addition, it can make your program more readable.
React tutorial: Types of Props for child components
Publish Date:2025/03/16 Views:170 Category:React
-
Usually, the child components of a React component are a group, that is, the child components are an array. Introduction to Type of the Children Props.
How to solve the error Uncaught TypeError: Cannot read properties of undefined in
Publish Date:2025/03/16 Views:150 Category:React
-
In the process of React development, we often encounter some errors. Here we look at an error reported in App.js. The error is as follows: App.js:69 Uncaught TypeError: Cannot read properties of undefined (reading 'setState') at onInput
Why do you need to bind event handlers in React Class Components?
Publish Date:2025/03/16 Views:58 Category:React
-
When using React, we must have come across control components and event handlers. We need to use `.bind()` in the constructor of the custom component to bind these methods to the component instance. As shown in the following code:
Solution to the error "does not contain a default export" in React
Publish Date:2025/03/16 Views:187 Category:React
-
When we try to use `default import` to import from a module that does not have a `default export`, we get a "does not contain a default export" error. To fix the error, make sure the module has named exports and wrap the import in curly braces, e.g.
Error in React: Attempted import error 'X' is not exported from Solution
Publish Date:2025/03/16 Views:76 Category:React
-
In React, the error “Attempted import error 'X' is not exported from” in React.js occurs when we try to import a named import that does not exist in the specified file. To fix the error, make sure the module has named exports and you have not obfu