github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 23:52:05 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #873] Prisma strictUndefinedChecks #8476

New Issue
Closed
opened 2026-04-13 03:33:22 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 03:33:22 -05:00
Owner
Copy Link

Originally created by @bmichotte on GitHub (Dec 13, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/873

Describe the bug
Prisma 5.20.0 introduced a new (preview) feature which is strictUndefinedChecks which allows you to disallow undefined values, you have to set the value to Prisma.skip instead

If we have this selected and for example want to create a user with

    const response = await auth.api.signUpEmail({
        body: {
            name,
            email,
            password,
        },
    })

it produces an Error

          data: {
            id: "IrBhtCpliP7FiC-iik9Hw",
            name: "Some name",
            email: "some@email.com",
            emailVerified: false,
            image: undefined,
                   ~~~~~~~~~
            createdAt: new Date("2024-12-13T10:29:44.031Z"),
            updatedAt: new Date("2024-12-13T10:29:44.031Z"),
          },
          select: undefined
        })

    Invalid value for argument `data`: explicitly `undefined` values are not allowed.

To Reproduce
Steps to reproduce the behavior:

  1. Create a project with Prisma 5.20.0+
  2. Configure prisma with
generator client {
    provider        = "prisma-client-js"
    previewFeatures = ["strictUndefinedChecks"]
}
  1. create a user

Expected behavior
The correct change should be

image: someImage ?? Prisma.skip,
Originally created by @bmichotte on GitHub (Dec 13, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/873 **Describe the bug** [Prisma 5.20.0](https://github.com/prisma/prisma/releases/tag/5.20.0) introduced a new (preview) feature which is `strictUndefinedChecks` which allows you to disallow `undefined` values, you have to set the value to `Prisma.skip` instead If we have this selected and for example want to create a user with ```ts const response = await auth.api.signUpEmail({ body: { name, email, password, }, }) ``` it produces an Error ``` data: { id: "IrBhtCpliP7FiC-iik9Hw", name: "Some name", email: "some@email.com", emailVerified: false, image: undefined, ~~~~~~~~~ createdAt: new Date("2024-12-13T10:29:44.031Z"), updatedAt: new Date("2024-12-13T10:29:44.031Z"), }, select: undefined }) Invalid value for argument `data`: explicitly `undefined` values are not allowed. ``` **To Reproduce** Steps to reproduce the behavior: 1. Create a project with Prisma 5.20.0+ 2. Configure prisma with ```ts generator client { provider = "prisma-client-js" previewFeatures = ["strictUndefinedChecks"] } ``` 3. create a user **Expected behavior** The correct change should be ```ts image: someImage ?? Prisma.skip, ```
GiteaMirror added the locked label 2026-04-13 03:33:22 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#8476
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?