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

mongodb-adapter schema generation not supported #828

New Issue
Closed
opened 2026-03-13 08:06:06 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-03-13 08:06:06 -05:00
Owner
Copy Link

Originally created by @AsenCME on GitHub (Mar 11, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

As stated in the documentation, generating a mongodb schema is supposed to work.

Image

However, the following error appears when running the CLI:

preparing schema... 2025-03-11T11:56:36.206Z ERROR [Better Auth]: mongodb-adapter is not supported.

Looking the source code, it does indeed seem that only keysly, prisma and drizzle are supported and mongodb-adapter is not one of them despite the documentation saying otherwise.

Current vs. Expected behavior

Expected to work, throws error.

What version of Better Auth are you using?

1.23

Provide environment information

- OS: MacOS

Which area(s) are affected? (Select all that apply)

Package, Documentation

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  ...
  database: mongodbAdapter(client.db()),
  ...
});

Additional context

No response

Originally created by @AsenCME on GitHub (Mar 11, 2025). ### Is this suited for github? - [ ] Yes, this is suited for github ### To Reproduce As stated in the documentation, generating a mongodb schema is supposed to work. <img width="923" alt="Image" src="https://github.com/user-attachments/assets/e86203a9-06c8-4491-a983-f550990e2078" /> However, the following error appears when running the CLI: ``` preparing schema... 2025-03-11T11:56:36.206Z ERROR [Better Auth]: mongodb-adapter is not supported. ``` Looking the source code, it does indeed seem that only keysly, prisma and drizzle are supported and mongodb-adapter is not one of them despite the documentation saying otherwise. ### Current vs. Expected behavior Expected to work, throws error. ### What version of Better Auth are you using? 1.23 ### Provide environment information ```bash - OS: MacOS ``` ### Which area(s) are affected? (Select all that apply) Package, Documentation ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ ... database: mongodbAdapter(client.db()), ... }); ``` ### Additional context _No response_
GiteaMirror added the bug label 2026-03-13 08:06:06 -05:00
GiteaMirror commented 2026-03-13 08:06:07 -05:00
Author
Owner
Copy Link

@yohannesjoya commented on GitHub (Mar 11, 2025):

@AsenCME who is working on this? anyone started this?

@yohannesjoya commented on GitHub (Mar 11, 2025): @AsenCME who is working on this? anyone started this?
GiteaMirror commented 2026-03-13 08:06:07 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Mar 12, 2025):

Better Auth supports mongodb, not mongoose. Since it doesn't rely on schemas, there's no need for schema generation.

@Bekacru commented on GitHub (Mar 12, 2025): Better Auth supports mongodb, not mongoose. Since it doesn't rely on schemas, there's no need for schema generation.
GiteaMirror commented 2026-03-13 08:06:08 -05:00
Author
Owner
Copy Link

@AsenCME commented on GitHub (Mar 12, 2025):

In my case, the error message states "... 'mongodb-adapter' not supported". I have followed the documentation in setting it up with the MongoDb connection string, like this:

import { betterAuth } from "better-auth";
const client = new MongoClient(process.env.MONGO_URI);

export const auth = betterAuth({
  ...
  database: mongodbAdapter(client.db()),
  ...
});

Better-auth is not connected to mongoose correctly.

@AsenCME commented on GitHub (Mar 12, 2025): In my case, the error message states "... 'mongodb-adapter' not supported". I have followed the documentation in setting it up with the MongoDb connection string, like this: ``` import { betterAuth } from "better-auth"; const client = new MongoClient(process.env.MONGO_URI); export const auth = betterAuth({ ... database: mongodbAdapter(client.db()), ... }); ``` Better-auth is not connected to mongoose correctly.
GiteaMirror commented 2026-03-13 08:06:09 -05:00
Author
Owner
Copy Link

@xorweak commented on GitHub (Mar 13, 2025):

I'm facing this problem too.

@xorweak commented on GitHub (Mar 13, 2025): I'm facing this problem too.
GiteaMirror commented 2026-03-13 08:06:09 -05:00
Author
Owner
Copy Link

@yohannesjoya commented on GitHub (Mar 13, 2025):

the work around that worked for me is using prisma and mongodb as provider

@yohannesjoya commented on GitHub (Mar 13, 2025): the work around that worked for me is using prisma and mongodb as provider
GiteaMirror commented 2026-03-13 08:06:10 -05:00
Author
Owner
Copy Link

@Muhamed-Ragab commented on GitHub (Mar 14, 2025):

I have the same error
I tried with mongoose and MongoDB client

@Muhamed-Ragab commented on GitHub (Mar 14, 2025): I have the same error I tried with mongoose and MongoDB client
GiteaMirror commented 2026-03-13 08:06:11 -05:00
Author
Owner
Copy Link

@jiaweing commented on GitHub (Mar 21, 2025):

I'm having the same issue while the docs said it's possible

@jiaweing commented on GitHub (Mar 21, 2025): I'm having the same issue while the docs said it's possible
GiteaMirror commented 2026-03-13 08:06:11 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Mar 21, 2025):

If this issue is regarding the CLI, we recently removed mentions of generation related to MongoDB from the docs. MongoDB doesn't require a schema, and the CLI doesn't generate one either. The docs were incorrectly stating that it does.

@Bekacru commented on GitHub (Mar 21, 2025): If this issue is regarding the CLI, we recently removed mentions of `generation` related to MongoDB from the docs. MongoDB doesn't require a schema, and the CLI doesn't generate one either. The docs were incorrectly stating that it does.
GiteaMirror commented 2026-03-13 08:06:12 -05:00
Author
Owner
Copy Link

@xorweak commented on GitHub (Mar 22, 2025):

If this issue is regarding the CLI, we recently removed mentions of generation related to MongoDB from the docs. MongoDB doesn't require a schema, and the CLI doesn't generate one either. The docs were incorrectly stating that it does.

Oh, thanks for clarifying. Although mongodb does not require schema, it doesn't need to create indexes on the database?, I saw that you intend to add indexing support in the schema generation tool. Anyways, modifying the docs would be great to avoid confusion. 🤓😃

@xorweak commented on GitHub (Mar 22, 2025): > If this issue is regarding the CLI, we recently removed mentions of `generation` related to MongoDB from the docs. MongoDB doesn't require a schema, and the CLI doesn't generate one either. The docs were incorrectly stating that it does. Oh, thanks for clarifying. Although mongodb does not require schema, it doesn't need to create indexes on the database?, I saw that you intend to add indexing support in the schema generation tool. Anyways, modifying the docs would be great to avoid confusion. 🤓😃
GiteaMirror commented 2026-03-13 08:06:13 -05:00
Author
Owner
Copy Link

@arshx86 commented on GitHub (May 20, 2025):

okay it's not supported but then? we gotta create schemas ourself?

@arshx86 commented on GitHub (May 20, 2025): okay it's not supported but then? we gotta create schemas ourself?
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 bug
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#828
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?