For almost every .tsx file in my project TS7026: JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.

[wegry]

Bug Report

🔎 Search Terms

TS7026 no interface JSX.IntrinsicElements exists typescript 4.3 typescript 4.3 breaking changes.

🕗 Version & Regression Information

• This changed between versions 4.2.4 and 4.3.2

⏯ Playground Link

Playground link with relevant code

💻 Code

The tsconfig.json in our project

{
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "importHelpers": true,
    "importsNotUsedAsValues": "error",
    "incremental": true,
    "isolatedModules": true,
    "moduleResolution": "node",
    "noEmit": true,
    "noEmitOnError": true,
    "jsx": "react-jsxdev",
    "lib": ["dom", "ES2020"],
    "allowJs": true,
    "module": "ES2020",
    "resolveJsonModule": true,
    "strict": true,
    "target": "ES2020",
    "types": [],
    "useDefineForClassFields": true
  },
  "include": [
    "./typings.d.ts",
    "./react-table-config.d.ts",
    "app",
    "components",
    "pages"
  ],
  "exclude": ["**/node_modules", "**/.*/"]
}

🙁 Actual behavior

Using Yarn 3 with PnP and webpack 5. We're also using the ts fork checker plugin. With a project that built in [email protected], [email protected] errors has an error in every tsx file.

It's usually

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

But there are a few

TS2322: Type '{ title: string; }' is not assignable to type 'Props'.
  Property 'children' is missing in type '{ title: string; }' but required in type '{ children: any; title?: string; }'.

and

TS2307: Cannot find module 'react/jsx-dev-runtime' or its corresponding type declarations.

🙂 Expected behavior

There might be a few broken things from breaking changes, but the project should compile.

[MartinJohns]

This sounds like #41813. Tho that changed with version 4.2.1.

[wegry]

@MartinJohns is there a way to see which libraries are using a global namespace v. which are not? Maybe within the tsc command itself?

[wegry]

After doing a yarn up -R @types/react{,-dom} and bumping to @yarnpkg/[email protected], these errors were no more with [email protected].

edit: The updated versions that worked were @types/[email protected] and @types/[email protected].

[wegry]

I'm seeing this again with [email protected].

[MartinJohns]

Possibly related to #45681.

[abitwhy]

This may be caused by IED (like VSCode). When an update prompt appears, try updating it first.

Updates:
In my case, this must be caused by renaming a markup variable. Related node_modules source code has been changed unexpectedly by
the renaming plugin. I fix it by reinstalling the node_modules. (The updating IDE mentioned above should also be indirectly updated node to fix the problem.)

[ghost]

I just updated the VSCode and it solved the issue.