Type '{}' is not assignable to type 'ReactNode'.

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

“next”: “12.1.4”, “react”: “^17.0.2”, “react-dom”: “^17.0.2”, file tsconfig.json

{
  "compilerOptions": {
    "target": "es6",
    "esModuleInterop": true,
    "importHelpers": true,
    "allowSyntheticDefaultImports": true,
    "experimentalDecorators": true,
    "lib": [
      "dom",
      "dom.iterable",
      "esnext",
      "es5",
      "es6"
    ],
    "baseUrl": ".", // setting a value for baseUrl is required
    "paths": {
      "@/*": [
        "*"
      ],
      "~/*": [
        "*"
      ]
    },
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "declaration": true,
    "downlevelIteration": true,
    "noUnusedParameters": false,
    "noUnusedLocals": false,
    "incremental": true
  },
  "exclude": [
    "node_modules",
    ".next",
    ".vscode",
    "out"
  ],
  "include": [
    "**/styles/**/*",
    "**/*.ts",
    "**/*.tsx",
    "**/*.yml",
    "**/*.yaml",
    "**/*.css",
    "**/*.scss",
    "**/*",
    ".d.ts",
    "next-env.d.ts",
  ]
}

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

The issue is that after upgrading to the last nextjs version, I am getting the error Type 'Component<{}, any, any>' is not assignable to type 'Element | ElementClass | null' for all components that are imported dynamically. Workaround: Change dynamic import to normal import solves the issue

Expected Behavior

it should work.

To Reproduce

create a component and import it dynamically

[raphaelcamar]

I´m having the same issue. the app build doesn´t run correctly. Yesterday was running correctly. Today is broken

[Alexcsmbz]

I have the same problem 😦 ecosystem project: react-ts All dependencies in the project aren’t auto-updating and are hardcoded (without ^) yesterday it works correctly too, today it is broken.