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

v1.4.x iteration plan #1966

New Issue
Closed
opened 2026-03-13 09:17:28 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-03-13 09:17:28 -05:00
Owner
Copy Link

Originally created by @himself65 on GitHub (Sep 18, 2025).

Features

Enable database transaction by default

We will enable it for the adapter that supports it. Right now, I've seen that Neon DB might not support it. So we should find a way to detect whether db supports it.

Database join supports

https://github.com/better-auth/better-auth/pull/5730 by @ping-maxwell

This will improve the database performance and helps new features

Related to

use AsyncLocalStorage for context tracking

AsyncLocalStorage is a powerful API for a server-side library to track the state across the async context, especially for the API server.

This will need Cloudflare user to update their wrangler.toml

Dedicated React client-side SDK

https://github.com/better-auth/better-auth/pull/4822

Ship @better-auth/react SDK and use it in better-auth/react subpath. It will cover the SSR/RSC solution.

Set CORS header by default

Related: https://github.com/better-auth/better-auth/issues/4720

Set CORS headers by default, this is confusing for people have backend and frontend server

Originally created by @himself65 on GitHub (Sep 18, 2025). ## Features ### Enable database transaction by default We will enable it for the adapter that supports it. Right now, I've seen that Neon DB might not support it. So we should find a way to detect whether db supports it. ### Database `join` supports https://github.com/better-auth/better-auth/pull/5730 by @ping-maxwell This will improve the database performance and helps new features Related to - https://github.com/better-auth/better-auth/issues/1247 ### use `AsyncLocalStorage` for context tracking AsyncLocalStorage is a powerful API for a server-side library to track the state across the async context, especially for the API server. This will need Cloudflare user to update their `wrangler.toml` ### Dedicated React client-side SDK https://github.com/better-auth/better-auth/pull/4822 Ship `@better-auth/react` SDK and use it in `better-auth/react` subpath. It will cover the SSR/RSC solution. ### Set CORS header by default Related: https://github.com/better-auth/better-auth/issues/4720 Set CORS headers by default, this is confusing for people have backend and frontend server
GiteaMirror added the enhancement label 2026-03-13 09:17:28 -05:00
GiteaMirror commented 2026-03-13 09:17:29 -05:00
Author
Owner
Copy Link

@coderrshyam commented on GitHub (Sep 20, 2025):

@himself65 Nice! But with some more improvement this can be released as v2, you can create a dedicated package for each libraries like:-

  • @better-auth/core
  • @better-auth/react
  • @better-auth/next
  • @better-auth/nuxt
  • @better-auth/express

and so on.

Adding new features in a minor versions are not sounds good.

@coderrshyam commented on GitHub (Sep 20, 2025): @himself65 Nice! But with some more improvement this can be released as `v2`, you can create a dedicated package for each libraries like:- - `@better-auth/core` - `@better-auth/react` - `@better-auth/next` - `@better-auth/nuxt` - `@better-auth/express` and so on. Adding new features in a minor versions are not sounds good.
GiteaMirror commented 2026-03-13 09:17:30 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Sep 20, 2025):

@himself65 Nice! But with some more improvement this can be released as v2, you can create a dedicated package for each libraries like:-

  • @better-auth/core
  • @better-auth/react
  • @better-auth/next
  • @better-auth/nuxt
  • @better-auth/express

and so on.

Adding new features in a minor versions are not sounds good.

We do have plans to do this!

@ping-maxwell commented on GitHub (Sep 20, 2025): > [@himself65](https://github.com/himself65) Nice! But with some more improvement this can be released as `v2`, you can create a dedicated package for each libraries like:- > > * `@better-auth/core` > * `@better-auth/react` > * `@better-auth/next` > * `@better-auth/nuxt` > * `@better-auth/express` > > and so on. > > Adding new features in a minor versions are not sounds good. We do have plans to do this!
GiteaMirror commented 2026-03-13 09:17:30 -05:00
Author
Owner
Copy Link

@coderrshyam commented on GitHub (Sep 20, 2025):

We do have plans to do this!

"That’s great! Would you consider publishing a blog post with a roadmap outlining the future plans for better-auth?"

@coderrshyam commented on GitHub (Sep 20, 2025): > We do have plans to do this! "That’s great! Would you consider publishing a blog post with a roadmap outlining the future plans for better-auth?"
GiteaMirror commented 2026-03-13 09:17:31 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Sep 22, 2025):

We do have plans to do this!

"That’s great! Would you consider publishing a blog post with a roadmap outlining the future plans for better-auth?"

We will, before we ship the new minor version. No hurry

@himself65 commented on GitHub (Sep 22, 2025): > > We do have plans to do this! > > "That’s great! Would you consider publishing a blog post with a roadmap outlining the future plans for better-auth?" We will, before we ship the new minor version. No hurry
GiteaMirror commented 2026-03-13 09:17:31 -05:00
Author
Owner
Copy Link

@cnbrown04 commented on GitHub (Oct 9, 2025):

I know #4978 is mentioned for the a 1.4.x release, would it be beneficial to include it here so we can point to this issue if people have questions?

@cnbrown04 commented on GitHub (Oct 9, 2025): I know #4978 is mentioned for the a 1.4.x release, would it be beneficial to include it here so we can point to this issue if people have questions?
GiteaMirror commented 2026-03-13 09:17:32 -05:00
Author
Owner
Copy Link

@Eazash commented on GitHub (Oct 10, 2025):

@himself65 Could you also consider this release as a candidate to resolve #1070? A new @better-auth/vue package would be a great place to address the API change that is required without fussing about semver in the core of better-auth

@Eazash commented on GitHub (Oct 10, 2025): @himself65 Could you also consider this release as a candidate to resolve #1070? A new `@better-auth/vue` package would be a great place to address the API change that is required without fussing about semver in the core of better-auth
GiteaMirror commented 2026-03-13 09:17:33 -05:00
Author
Owner
Copy Link

@codingwithmizan commented on GitHub (Oct 20, 2025):

I have a separate backend (REST API) built with Ruby on Rails and a frontend application developed using Next.js (App Router).The backend sends an access_token after a successful login, but I’m having trouble handling authentication on the frontend.Can anyone help me figure out the best way to manage authentication between the two apps using better-auth?

@codingwithmizan commented on GitHub (Oct 20, 2025): I have a separate backend (REST API) built with Ruby on Rails and a frontend application developed using Next.js (App Router).The backend sends an access_token after a successful login, but I’m having trouble handling authentication on the frontend.Can anyone help me figure out the best way to manage authentication between the two apps using better-auth?
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
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#1966
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?