Skip to content
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

Build fails when consuming application uses TS exactOptionalPropertyTypes. #35280

Closed
1 task done
quisido opened this issue Mar 13, 2022 · 1 comment · Fixed by #35281
Closed
1 task done

Build fails when consuming application uses TS exactOptionalPropertyTypes. #35280

quisido opened this issue Mar 13, 2022 · 1 comment · Fixed by #35281
Labels
bug Issue was opened via the bug report template.

Comments

@quisido
Copy link
Contributor

quisido commented Mar 13, 2022

Verify canary release

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

Provide environment information

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 3.1.1
      pnpm: N/A
    Relevant packages:
      next: 12.1.1-canary.10
      react: 17.0.2
      react-dom: 17.0.2

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

An error is thrown when running next build on any TypeScript+Next app where TS's compilerOptions.exactOptionalPropertyTypes is set to true.

image

Expected Behavior

I expect the build is complete successfully, as you can see in this screenshot after I patched it with the accompanying pull request:

image

To Reproduce

Set compilerOptions.exactOptionalPropertyTypes to true on any Next app, then run next build.

@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant