-
Notifications
You must be signed in to change notification settings - Fork 26.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong TypeScript export signature for next/jest #36534
Labels
Comments
timneutkens
added
kind: bug
TypeScript
Related to types with Next.js.
Testing
Related to testing with Next.js.
and removed
bug
Issue was opened via the bug report template.
labels
Apr 28, 2022
3 tasks
SukkaW
added a commit
to SukkaW/next.js
that referenced
this issue
May 11, 2022
SukkaW
added a commit
to SukkaW/next.js
that referenced
this issue
May 11, 2022
SukkaW
added a commit
to SukkaW/next.js
that referenced
this issue
May 11, 2022
ijjk
pushed a commit
that referenced
this issue
May 11, 2022
1 task
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Verify canary release
Provide environment information
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 suchdefault
property.Expected Behavior
jest.d.ts
usesexport =
instead ofexport default
.To Reproduce
The text was updated successfully, but these errors were encountered: