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

[GH-ISSUE #6112] Documentation Update for Prisma v7 Patterns #19053

New Issue
Closed
opened 2026-04-15 17:50:12 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-15 17:50:12 -05:00
Owner
Copy Link

Originally created by @JeffreyLind3 on GitHub (Nov 19, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6112

As of Prisma v7, the official way to import PrismaClient is:

import { PrismaClient } from "@/generated/prisma/client";

As far as my understanding goes, the below import is no longer valid like it was in v6:

import { PrismaClient } from "@prisma/client";

(Sources: YouTube, Migration Guide)

Thus, the documentation page for Prisma (docs/content/docs/adapters/prisma.mdx) needs to be updated to update this import path and delete the Alert Callout below:

<Callout type="warning">
  If you have configured a custom output directory in your `schema.prisma` file (e.g., `output = "../src/generated/prisma"`), make sure to import the Prisma client from that location instead of `@prisma/client`. Learn more about custom output directories in the [Prisma documentation](https://www.prisma.io/docs/guides/nextjs#21-install-prisma-orm-and-create-your-first-models).
</Callout>

Additionally, now there are adapter packages that have to explicitly be used, such as @prisma/adapter-pg for Postgres, @prisma/adapter-better-sqlite3 for SQLite, and more. This probably also warrants an update to the code block in this doc page as well.

I'd submit a PR but I am not a Prisma guru so will leave it to someone who knows better than me!

Originally created by @JeffreyLind3 on GitHub (Nov 19, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6112 As of Prisma v7, the official way to import `PrismaClient` is: ```typescript import { PrismaClient } from "@/generated/prisma/client"; ``` As far as my understanding goes, the below import is no longer valid like it was in v6: ```typescript import { PrismaClient } from "@prisma/client"; ``` (Sources: [YouTube](https://www.youtube.com/watch?v=AmIXJHL-sBU), [Migration Guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7?utm_source=blog&utm_content=launch-blog&via=prisma7&utm_campaign=prisma7)) Thus, the documentation page for Prisma (`docs/content/docs/adapters/prisma.mdx`) needs to be updated to update this import path and delete the Alert Callout below: ```typescript <Callout type="warning"> If you have configured a custom output directory in your `schema.prisma` file (e.g., `output = "../src/generated/prisma"`), make sure to import the Prisma client from that location instead of `@prisma/client`. Learn more about custom output directories in the [Prisma documentation](https://www.prisma.io/docs/guides/nextjs#21-install-prisma-orm-and-create-your-first-models). </Callout> ``` Additionally, now there are adapter packages that have to explicitly be used, such as `@prisma/adapter-pg` for Postgres, `@prisma/adapter-better-sqlite3` for SQLite, and more. This probably also warrants an update to the code block in this doc page as well. I'd submit a PR but I am not a Prisma guru so will leave it to someone who knows better than me!
GiteaMirror added the locked label 2026-04-15 17:50:12 -05:00
GiteaMirror commented 2026-04-15 17:50:14 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Nov 19, 2025):

Thanks for opening this issue! We appreciate your suggestion regarding the Prisma v7 update. We'll review the Prisma adapter documentation to update the import path to use the official guidance—for instance, importing with "@/generated/prisma/client"—and remove the outdated alert about custom output directories. Our docs team will work on aligning the documentation with the Prisma v7 standards. In the meantime, could you let us know if there are any other related updates you think might be needed? tag @better-auth-agent if you would like an answer from the Agent.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3555069437 --> @better-auth-agent[bot] commented on GitHub (Nov 19, 2025): Thanks for opening this issue! We appreciate your suggestion regarding the Prisma v7 update. We'll review the Prisma adapter documentation to update the import path to use the official guidance—for instance, importing with "@/generated/prisma/client"—and remove the outdated alert about custom output directories. Our docs team will work on aligning the documentation with the Prisma v7 standards. In the meantime, could you let us know if there are any other related updates you think might be needed? tag @better-auth-agent if you would like an answer from the Agent. <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)
GiteaMirror commented 2026-04-15 17:50:14 -05:00
Author
Owner
Copy Link

@GautamBytes commented on GitHub (Nov 20, 2025):

taking this into my task bucket list!

<!-- gh-comment-id:3557416628 --> @GautamBytes commented on GitHub (Nov 20, 2025): taking this into my task bucket list!
GiteaMirror commented 2026-04-15 17:50:15 -05:00
Author
Owner
Copy Link

@JeffreyLind3 commented on GitHub (Nov 21, 2025):

Fixed with #6133

<!-- gh-comment-id:3563776853 --> @JeffreyLind3 commented on GitHub (Nov 21, 2025): Fixed with #6133
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#19053
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?