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

Any plans for Redwood support? #80

New Issue
Closed
opened 2026-03-13 07:32:09 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 07:32:09 -05:00
Owner
Copy Link

Originally created by @knajjars on GitHub (Oct 15, 2024).

Originally created by @knajjars on GitHub (Oct 15, 2024).
GiteaMirror added the enhancementquestion labels 2026-03-13 07:32:10 -05:00
GiteaMirror commented 2026-03-13 07:32:13 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Oct 16, 2024):

I'm not familiar with Redwood, but it should already be supported if it:

  • Supports API endpoints/routes
  • Works with either the Web Standard Request/Response objects or Node.js using the Node adapter.
  • Supports catch-all routes.
@Bekacru commented on GitHub (Oct 16, 2024): I'm not familiar with Redwood, but it should already be supported if it: - Supports API endpoints/routes - Works with either the Web Standard Request/Response objects or Node.js using the Node adapter. - Supports catch-all routes.
GiteaMirror commented 2026-03-13 07:32:14 -05:00
Author
Owner
Copy Link

@KelechiOdom10 commented on GitHub (Oct 16, 2024):

Also Redwood already has built-in auth baked into the framework. I'm not sure why we'd want to mix both!

@KelechiOdom10 commented on GitHub (Oct 16, 2024): Also Redwood already has built-in auth baked into the framework. I'm not sure why we'd want to mix both!
GiteaMirror commented 2026-03-13 07:32:15 -05:00
Author
Owner
Copy Link

@knajjars commented on GitHub (Oct 16, 2024):

Also Redwood already has built-in auth baked into the framework. I'm not sure why we'd want to mix both!

I think that is fair, although Redwood's auth is very limited compared to the features offered by better-auth. Also they offer setup for many different providers via their CLI (Supabase Auth, Firebase Auth, Custom, In-House solution, etc.).

@knajjars commented on GitHub (Oct 16, 2024): > Also Redwood already has built-in auth baked into the framework. I'm not sure why we'd want to mix both! I think that is fair, although Redwood's auth is very limited compared to the features offered by better-auth. Also they offer setup for many different providers via their CLI (Supabase Auth, Firebase Auth, Custom, In-House solution, etc.).
GiteaMirror commented 2026-03-13 07:32:16 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Dec 17, 2024):

We don't have plans to directly support Redwood at the moment. I think this will mostly involve providing a guide. We're always open to a PR for adding a guide on how to integrate Better Auth with Redwood. I'm going to close this as not planned.

@Bekacru commented on GitHub (Dec 17, 2024): We don't have plans to directly support Redwood at the moment. I think this will mostly involve providing a guide. We're always open to a PR for adding a guide on how to integrate Better Auth with Redwood. I'm going to close this as not planned.
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 question
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#80
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?