TypeScript error when importing next/image with "type": "module" and "moduleResolution": "nodenext"

[michaelhays]

Verify canary release

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

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: N/A
      pnpm: 7.29.1
    Relevant packages:
      next: 13.2.5-canary.8
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

TypeScript

Link to the code that reproduces this issue

https://github.com/michaelhays/next-ts-import

To Reproduce

In a new Next.js project, add "type": "module" to package.json, and set "moduleResolution": "nodenext" in tsconfig.json.

Importing next/image (or any next/* package) throws a TypeScript error, though the package is actually found when running the app.

Describe the Bug

Expected Behavior

The import should be found by TypeScript.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[balazsorban44]

Duplicate of #46078

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.