Type definitions of exports are invalid #46689
Labels
bug
Issue was opened via the bug report template.
locked
stale
The issue has not seen recent activity.
TypeScript
Related to types with Next.js.
Verify 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:
Run
npm install
, then typecheck usingnpx 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
The text was updated successfully, but these errors were encountered: