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

[GH-ISSUE #3148] Add Prisma schema file name for CLI generate #9491

New Issue
Closed
opened 2026-04-13 04:58:30 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 04:58:30 -05:00
Owner
Copy Link

Originally created by @lucafaggianelli on GitHub (Jun 23, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3148

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

I'm using Prisma with multiple schema files (i.e. a prisma/ folder with multiple .prisma files) and when I run the npx @better-auth/cli generate command the main prisma schema file is overwritten, whereas my auth-related schema is in another prisma schema file (prisma/auth.prisma)

Describe the solution you'd like

I'd like to specify the path to the right Prisma schema file in the generate command, something similar to the --config option to specify auth.ts location.

Describe alternatives you've considered

As of today I run the command and then I move the generated schema manually

Additional context

No response

Originally created by @lucafaggianelli on GitHub (Jun 23, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3148 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I'm using Prisma with multiple schema files (i.e. a `prisma/` folder with multiple `.prisma` files) and when I run the `npx @better-auth/cli generate` command the main prisma schema file is overwritten, whereas my auth-related schema is in another prisma schema file (`prisma/auth.prisma`) ### Describe the solution you'd like I'd like to specify the path to the right Prisma schema file in the `generate` command, something similar to the `--config` option to specify `auth.ts` location. ### Describe alternatives you've considered As of today I run the command and then I move the generated schema manually ### Additional context _No response_
GiteaMirror added the enhancementlocked labels 2026-04-13 04:58:30 -05:00
GiteaMirror commented 2026-04-13 04:58:32 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 22, 2025):

Hi, @lucafaggianelli. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a feature for the npx @better-auth/cli generate command to specify a Prisma schema file path.
  • The goal is to avoid overwriting the main schema when multiple .prisma files exist.
  • Currently, the CLI defaults to the main schema, requiring manual file moves after generation.
  • You suggested adding an option similar to the existing --config flag to specify schema file locations.
  • There has been no further activity or comments on this issue.

Next Steps:

  • Please let me know if this feature request is still relevant with the latest version of better-auth by commenting on this issue.
  • If I do not hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3319921246 --> @dosubot[bot] commented on GitHub (Sep 22, 2025): Hi, @lucafaggianelli. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested a feature for the `npx @better-auth/cli generate` command to specify a Prisma schema file path. - The goal is to avoid overwriting the main schema when multiple `.prisma` files exist. - Currently, the CLI defaults to the main schema, requiring manual file moves after generation. - You suggested adding an option similar to the existing `--config` flag to specify schema file locations. - There has been no further activity or comments on this issue. **Next Steps:** - Please let me know if this feature request is still relevant with the latest version of better-auth by commenting on this issue. - If I do not hear back within 7 days, I will automatically close this issue. Thank you for your understanding and contribution!
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 enhancement 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#9491
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?