TypeScript Error: Unexpected token `div`. Expected jsx identifier
Matthew C.
The Problem
You are building a Next.js app and encounter the following error:
Error: Unexpected token `div`. Expected jsx identifier
As an example, adding the following code to the /src/app/page.tsx file will cause the error:
export default function Home() { const casesArr = [{ id: 1, name: "Case 1" }, { id: 2, name: "Case 2" }, { id: 3, name: "Case 3" }]; return ( <div> <ul> {casesArr.map((case) => ( <li key={case.id}>{case.name}</li> ))} </ul> </div> ); }
The Unexpected token error is a JavaScript syntax error. It occurs when a specific language construct is expected but not provided. In this case, TypeScript was expecting JSX to be returned but came across something unexpected.
The Solution
The issue may be due to a typo. It can also be due to using reserved JavaScript words, missing property values, extra or missing parentheses, or due to a trailing comma being in a place where an expression is expected.
Don’t Use Reserved JavaScript Words
To fix the code example above, change the name of the callback function argument in the map array method:
export default function Home() { const casesArr = [{ id: 1, name: "Case 1" }, { id: 2, name: "Case 2" }, { id: 3, name: "Case 3" }]; return ( <div> <ul> {casesArr.map((caseItem) => ( <li key={caseItem.id}>{caseItem.name}</li> ))} </ul> </div> ); }
The word case is a reserved word in JavaScript. You can’t use reserved words as identifiers for variables, functions, classes, etc.
Missing Property Palue
The error can also be caused by a missing property value:
<Image src="/next.svg" alt="logo" width={} height={200} />
Extra Parentheses or Missing Parentheses
An extra parenthesis can cause the issue:
<Image src="/next.svg" alt="logo" width={20} height={200}} />
Missing parentheses can also cause an error:
<Image src="/next.svg" alt="logo" width={20} height={200 />
Expression Expected
If you add a trailing comma where an expression is expected, such as after a map() function, you’ll get the error:
<ul> {casesArr.map((caseItem) => ( <li key={caseItem.id}>{caseItem.name}</li> )),} </ul>
You can fix the error by removing the comma, or by adding an expression like:
<ul> {casesArr.map((caseItem) => ( <li key={caseItem.id}>{caseItem.name}</li> )).reverse()} </ul>
Get Started With Sentry
Get actionable, code-level insights to resolve Next.js performance bottlenecks and errors.
Run the line of code below to:
Create a free Sentry account
Run the CLI install command to automatically add the Sentry SDK to your project:
Click to Copynpx @sentry/wizard@latest -i nextjsStart capturing errors and performance issues
Loved by over 4 million developers and more than 90,000 organizations worldwide, Sentry provides code-level observability to many of the world’s best-known companies like Disney, Peloton, Cloudflare, Eventbrite, Slack, Supercell, and Rockstar Games. Each month we process billions of exceptions from the most popular products on the internet.
Related Answers
- Can you use Next.js with a React Native App?
- Error: Importing a component that needs useState. It only works in a Client Component, but none of its parents are marked with use client, so they're Server Components by default.
- Error: There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering
- Error: NextRouter was not mounted
- Get URL Params Next.js 13
- Fixing handleHardNavigation errors in Next.js
- How can I get query parameters from the URL?
- How to allow domains for images in Next.js
- Is it possible to set a server-side cookie in Next.js?
- Fixing "Module not found" errors in Next.js
A better experience for your users. An easier life for your developers.
A peek at your privacy
Here’s a quick look at how Sentry handles your personal information (PII).
×Who we collect PII from
We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?PII we may collect about you
- PII provided by you and related to your
- Account, profile, and login
- Requests and inquiries
- Purchases
- PII collected from your device and usage
- PII collected from third parties (e.g., social media)
How we use your PII
- To operate our site and service
- To protect and improve our site and service
- To provide customer care and support
- To communicate with you
- For other purposes (that we inform you of at collection)
Third parties who receive your PII
We may disclose your PII to the following type of recipients:
- Subsidiaries and other affiliates
- Service providers
- Partners (go-to-market, analytics)
- Third-party platforms (when you connect them to our service)
- Governmental authorities (where necessary)
- An actual or potential buyer
We use cookies (but not for advertising)
- We do not use advertising or targeting cookies
- We use necessary cookies to run and improve our site and service
- You can disable cookies but this can impact your use or access to certain parts of our site and service
Know your rights
You may have the following rights related to your PII:
- Access, correct, and update
- Object to or restrict processing
- Port over
- Opt-out of marketing
- Be forgotten by Sentry
- Withdraw your consent
- Complain about us
If you have any questions or concerns about your privacy at Sentry, please email us at compliance@sentry.io.
If you are a California resident, see our Supplemental notice.