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

[PR #2209] [MERGED] docs(hono): add client-side auth (hono RPC) configuration guide #12444

New Issue
Closed
opened 2026-04-13 08:23:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 08:23:07 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/2209
Author: @braden-w
Created: 4/10/2025
Status: ✅ Merged
Merged: 4/11/2025
Merged by: @Bekacru

Base: main ← Head: patch-1

📝 Commits (1)

  • 5da2081 docs(hono): add client-side auth configuration guide

📊 Changes

1 file changed (+30 additions, -0 deletions)

View changed files

📝 docs/content/docs/integrations/hono.mdx (+30 -0)

📄 Description

This PR is part of a stack, managed by mrge:

Description

Added documentation for configuring the Hono client to properly handle cross-origin authentication requests. This is a common pain point for developers when setting up Better Auth with Hono, especially during local development when the client and server are on different ports.

Changes

  • Added new "Client-Side Configuration" section to the Hono Integration docs
  • Provided TypeScript example for configuring the Hono client
  • Added notes about cross-origin authentication requirements
  • Connected the client-side setup with existing CORS documentation

Context

While implementing Better Auth with Hono in our own application, I encountered issues with cross-origin cookie transmission. The solution wasn't immediately obvious from the existing documentation, so this PR adds clear guidance for other developers who might face the same challenge.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/2209 **Author:** [@braden-w](https://github.com/braden-w) **Created:** 4/10/2025 **Status:** ✅ Merged **Merged:** 4/11/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`5da2081`](https://github.com/better-auth/better-auth/commit/5da2081f9d19294213ca3b4449f187565abb9484) docs(hono): add client-side auth configuration guide ### 📊 Changes **1 file changed** (+30 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/integrations/hono.mdx` (+30 -0) </details> ### 📄 Description <!-- MRGE_STACK_DESCRIPTION_START --> This PR is part of a [stack](https://docs.mrge.io/overview), managed by [mrge](https://mrge.io): * `main` (default branch) * [#1538: feat(organization): Add dynamic role authorization](https://github.com/better-auth/better-auth/pull/1538) * **[#2209: docs(hono): add client-side auth (hono RPC) configuration guide](https://github.com/better-auth/better-auth/pull/2209)** ⬅️ Current PR ([View on mrge](https://mrge.io/pr/better-auth/better-auth/pull/2209)) --- <!-- MRGE_STACK_DESCRIPTION_END --> ## Description Added documentation for configuring the Hono client to properly handle cross-origin authentication requests. This is a common pain point for developers when setting up Better Auth with Hono, especially during local development when the client and server are on different ports. ### Changes - Added new "Client-Side Configuration" section to the Hono Integration docs - Provided TypeScript example for configuring the Hono client - Added notes about cross-origin authentication requirements - Connected the client-side setup with existing CORS documentation ### Context While implementing Better Auth with Hono in our own application, I encountered issues with cross-origin cookie transmission. The solution wasn't immediately obvious from the existing documentation, so this PR adds clear guidance for other developers who might face the same challenge. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 08:23:07 -05:00
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 pull-request
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#12444
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?