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

betterAuth callback for configuration #1688

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

Originally created by @bestickley on GitHub (Aug 12, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

I want to be able to configure betterAuth options without running at module level scope. This causes issues when I run next build for example, and env vars are only available at request time.

Describe the solution you'd like

I want to be able to configure betterAuth with a callback instead of an object.

betterAuth(() => {
  const plugins = [];
  if (process.env.IDP_TYPE === "cognito") {
    plugins.push(genericOAuth(...));
  }  else {
    ..
  }
  return { plugins, ... };
})

Describe alternatives you've considered

Running this logic at module level scope.

Additional context

No response

Originally created by @bestickley on GitHub (Aug 12, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I want to be able to configure `betterAuth` options without running at module level scope. This causes issues when I run `next build` for example, and env vars are only available at request time. ### Describe the solution you'd like I want to be able to configure `betterAuth` with a callback instead of an object. ```ts betterAuth(() => { const plugins = []; if (process.env.IDP_TYPE === "cognito") { plugins.push(genericOAuth(...)); } else { .. } return { plugins, ... }; }) ``` ### Describe alternatives you've considered Running this logic at module level scope. ### Additional context _No response_
GiteaMirror added the nextjs label 2026-03-13 08:56:31 -05:00
GiteaMirror commented 2026-03-13 08:56:33 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Aug 12, 2025):

Would loading dynamically once you have ENVs work for you?

@ping-maxwell commented on GitHub (Aug 12, 2025): Would loading dynamically once you have ENVs work for you?
GiteaMirror commented 2026-03-13 08:56:33 -05:00
Author
Owner
Copy Link

@bestickley commented on GitHub (Aug 13, 2025):

@ping-maxwell, not sure what you mean. Could you elaborate with code?

@bestickley commented on GitHub (Aug 13, 2025): @ping-maxwell, not sure what you mean. Could you elaborate with code?
GiteaMirror commented 2026-03-13 08:56:34 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (Aug 13, 2025):

Right now, Better Auth is initialized at module scope with a static options object passed to betterAuth(...) during setup. This keeps plugin wiring and other configurations consistent, ensuring type safety, security, and predictable runtime behavior. but there might be a hack to this. Moving this to a request-level setup would add overhead and could also break important capabilities like accurate type inference and certain APIs that depend on a stable, statically exposed auth instance. but if can be able to mitigate all those trade-off while maintaining the runtime safety that would be a good thing to have.

@Kinfe123 commented on GitHub (Aug 13, 2025): Right now, Better Auth is initialized at module scope with a static options object passed to betterAuth(...) during setup. This keeps plugin wiring and other configurations consistent, ensuring type safety, security, and predictable runtime behavior. but there might be a hack to this. Moving this to a request-level setup would add overhead and could also break important capabilities like accurate type inference and certain APIs that depend on a stable, statically exposed auth instance. but if can be able to mitigate all those trade-off while maintaining the runtime safety that would be a good thing to have.
GiteaMirror commented 2026-03-13 08:56:34 -05:00
Author
Owner
Copy Link

@JJosephttg commented on GitHub (Dec 5, 2025):

I think it is valuable to have for NestJS specifically. There are services we need to talk to that only show up at bootstrap time. For plugins like stripe, there is no way for us to talk to module based dependencies, which could be crucial for our flow

@JJosephttg commented on GitHub (Dec 5, 2025): I think it is valuable to have for NestJS specifically. There are services we need to talk to that only show up at bootstrap time. For plugins like stripe, there is no way for us to talk to module based dependencies, which could be crucial for our flow
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 nextjs
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#1688
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?