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

Sveltekit actions error #1150

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

Originally created by @weepy on GitHub (May 1, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. create a typical sveltekit project
  2. add a hooks.server.js file

Current vs. Expected behavior

Hiya,
I've integrated better-auth into my sveltekit app. All going smoothly until i git the actions.

I have a hooks.server.js that looks like:

import { auth } from "$lib/auth"; // path to your auth file
import { svelteKitHandler } from "better-auth/svelte-kit";

export async function handle({ event, resolve }) {
    svelteKitHandler({ event, resolve, auth });
    const session = await auth.api.getSession({
        headers: event.request.headers
    })
   
    if (!session) {
        return new Response("Unauthorized", { status: 401 })
    }
    event.locals.session = session?.session;
    event.locals.user = session?.user;
    return resolve(event);
}

which is all groovy, but then when I try and grab stuff from the body in an action ...
E.g.


export async function POST({  reques, locals }) {
    const body = await request.json(); // <<<<< Error: Body is not usable.

I get this error because I guess the sveltekitHandler has already done this.

How should I handle this ?

What version of Better Auth are you using?

latest

Provide environment information

- Chrome, Macos

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

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
});

Additional context

No response

Originally created by @weepy on GitHub (May 1, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. create a typical sveltekit project 2. add a hooks.server.js file ### Current vs. Expected behavior Hiya, I've integrated better-auth into my sveltekit app. All going smoothly until i git the actions. I have a hooks.server.js that looks like: ```js import { auth } from "$lib/auth"; // path to your auth file import { svelteKitHandler } from "better-auth/svelte-kit"; export async function handle({ event, resolve }) { svelteKitHandler({ event, resolve, auth }); const session = await auth.api.getSession({ headers: event.request.headers }) if (!session) { return new Response("Unauthorized", { status: 401 }) } event.locals.session = session?.session; event.locals.user = session?.user; return resolve(event); } ```` which is all groovy, but then when I try and grab stuff from the body in an action ... E.g. ```js export async function POST({ reques, locals }) { const body = await request.json(); // <<<<< Error: Body is not usable. ```` I get this error because I guess the sveltekitHandler has already done this. How should I handle this ? ### What version of Better Auth are you using? latest ### Provide environment information ```bash - Chrome, Macos ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context _No response_
GiteaMirror commented 2026-03-13 08:25:13 -05:00
Author
Owner
Copy Link

@ezShroom commented on GitHub (Jun 16, 2025):

@weepy how did you solve this?

@ezShroom commented on GitHub (Jun 16, 2025): @weepy how did you solve this?
GiteaMirror commented 2026-03-13 08:25:14 -05:00
Author
Owner
Copy Link

@weepy commented on GitHub (Jun 16, 2025):

I solved it by not using better-auth

@weepy commented on GitHub (Jun 16, 2025): I solved it by not using better-auth
GiteaMirror commented 2026-03-13 08:25:15 -05:00
Author
Owner
Copy Link

@screenfluent commented on GitHub (Jul 9, 2025):

I solved it by not using better-auth

What did you choose? Or maybe own auth as I'm about to ditch it as well...

@screenfluent commented on GitHub (Jul 9, 2025): > I solved it by not using better-auth What did you choose? Or maybe own auth as I'm about to ditch it as well...
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
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#1150
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?