JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists

avatar
Borislav Hadzhiev

Last updated: Feb 29, 2024
3 min

banner

# JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists

To solve the error "JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists", make sure to install the typings for react and restart your IDE.

jsx element implicitly has type any

Open your terminal in your project's root directory (where your package.json file is located) and run the following command:

shell
# ๐Ÿ‘‡๏ธ with NPM npm install --save-dev @types/react@latest @types/react-dom@latest # ๐Ÿ‘‡๏ธ if you also want to update react and react-dom npm install react@latest react-dom@latest # ------------------------------ # ๐Ÿ‘‡๏ธ with YARN yarn add @types/react@latest @types/react-dom@latest --dev # ๐Ÿ‘‡๏ธ if you also want to update react and react-dom yarn add react@latest react-dom@latest
The code for this article is available on GitHub

The command will update the versions of your react typings.

Make sure that the jsx option in your tsconfig.json file is set to react-jsx.
tsconfig.json
{ "compilerOptions": { // ๐Ÿ‘‡๏ธ make sure it's set to react-jsx "jsx": "react-jsx" // ... rest }, // ... rest }

When the jsx option is set to react-jsx, it causes the compiler to emit .js files with the JSX changed to _jsx calls.

Make sure to restart your development server and your IDE if necessary. Your dev server won't pick up the changes until you stop it and re-run the npm start command.

# Delete your node_modules and reinstall your dependencies

If the error is not resolved, try to delete your node_modules and package-lock.json (not package.json) files, re-run npm install and restart your IDE.

If you are on macOS or Linux, issue the following commands in bash or zsh.

shell
# for macOS and Linux rm -rf node_modules rm -f package-lock.json rm -f yarn.lock # ๐Ÿ‘‡๏ธ clean npm cache npm cache clean --force # ๐Ÿ‘‡๏ธ install packages npm install

If you are on Windows, issue the following commands in CMD.

cmd
# for Windows rd /s /q "node_modules" del package-lock.json del -f yarn.lock # ๐Ÿ‘‡๏ธ clean npm cache npm cache clean --force # ๐Ÿ‘‡๏ธ install packages npm install
Make sure to restart your IDE and dev server if the error persists. VSCode often glitches and a reboot solves things sometimes.

If you use VS Code, you can restart your IDE by clicking CTRL + Shift + P or (โŒ˜ + Shift + P on Mac) to open the command palette and type and select Reload Window.

Want to learn more about using React with TypeScript? Check out these resources: Parameter 'event' implicitly has 'any' type in React,Parameter 'props' implicitly has 'any' type in React.

# Verify the typings for React are installed

If you still get the error, open your package.json file and make sure it contains the @types/react package in the devDependencies object.

package.json
{ // ... rest "dependencies": { "react": "^18.0.0", "react-dom": "^18.0.0", }, "devDependencies": { "@types/react": "^18.0.5", "@types/react-dom": "^18.0.1", } }
The code for this article is available on GitHub

You can try to manually add the lines and re-run npm install.

shell
npm install

Or install the latest version of the package:

shell
# ๐Ÿ‘‡๏ธ with NPM npm install --save-dev @types/react@latest @types/react-dom@latest # ๐Ÿ‘‡๏ธ if you also want to update react and react-dom npm install react@latest react-dom@latest # ------------------------------ # ๐Ÿ‘‡๏ธ with YARN yarn add @types/react@latest @types/react-dom@latest --dev # ๐Ÿ‘‡๏ธ if you also want to update react and react-dom yarn add react@latest react-dom@latest

If you define a component that starts with a lowercase letter, you'd get the Property does not exist on type 'JSX.IntrinsicElements' error.

I wrote a book in which I share everything I know about how to become a better, more efficient programmer.
book cover
You can use the search field on my Home Page to filter through all of my articles.

Copyright ยฉ 2024 Borislav Hadzhiev