Wrong TypeScript export signature for next/jest

[alex-4ed5ec60d]

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 21.4.0: Mon Feb 21 20:35:58 PST 2022; root:xnu-8020.101.4~2/RELEASE_ARM64_T6000
Binaries:
  Node: 16.13.2
  npm: 8.1.2
  Yarn: 1.22.18
  pnpm: 6.32.4
Relevant packages:
  next: 12.1.4
  react: 17.0.2
  react-dom: 17.0.2

What browser are you using? (if relevant)

N/A

How are you deploying your application? (if relevant)

N/A

Describe the Bug

The TypeScript definition requires writing require('next/jest').default to access the function while in the actual code, there is no such default property.

Expected Behavior

jest.d.ts uses export = instead of export default.

To Reproduce

// @ts-check
const nextJest = require('next/jest');

// ❌ TS2349: Cannot invoke an expression whose type lacks a call signature.
const config = nextJest();

// ❌ Uncaught TypeError: nextJest.default is not a function
const config = nextJest.default();

[ryami333]

@ijjk Please reopen: the error still persists after #36534. Please see my minimal reproducible example demonstrating it on 12.1.7-canary here or track my other issue (#37524) for more details.

[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.