Type definitions of exports are invalid

[remcohaszing]

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: #202302091138~1675975749~22.04~f771a7f SMP PREEMPT_DYNAMIC Thu F
    Binaries:
      Node: 19.7.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 7.27.0
    Relevant packages:
      next: 13.2.4-canary.0
      eslint-config-next: N/A
      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

N/A (not a runtime issue)

To Reproduce

Create a project with the following files:

// package.json
{
  "dependencies": {
    "@types/node": "^18.0.0",
    "@types/react": "18.0.0",
    "@types/react-dom": "^18.0.0",
    "next": "canary",
    "typescript": "^4.0.0"
  }
}

// tsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "jsx": "react-jsx",
    "noEmit": true
  }
}

// index.ts
import App from 'next/app'

const app = <App />

Run npm install, then typecheck using npx tsc.

Describe the Bug

This will show various errors. They are all related to Next.js using `esModuleInterop. Because of this, Next.js packages are affected by microsoft/TypeScript#52779.

Typical Next.js users don’t see this bug, because Next.js enforces people to use esModuleInterop, which hides the issue, but shouldn’t be necessary.

Expected Behavior

Next.js packages have proper type exports. This can be ensured by building without the esModuleInterop option.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!

[github-actions]

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