N
Nuxt•3w ago
lazygopher

Modify event in handler before passing to a better-auth lib

I'm using better-auth as auth library I'm using their example for handling auth functionality 
export default defineEventHandler((event) => {
    return auth.handler(toWebRequest(event))
})
export default defineEventHandler((event) => {
    return auth.handler(toWebRequest(event))
})
Now I need to modify the body as I want to patch the image field of the body. How can I do that? something like export default defineEventHandler((event) => { const body = await readBody(event) const modifiedBody = { ...body, image: body.image || ..., } // patch event (don't think it's possible since its ready-only?) OR create a new event that I can pass to toWebRequest function return auth.handler(toWebRequest(event)) })
5 Replies
kapa.ai
kapa.ai•3w ago
Hi @lazygopher. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- I'm sorry, but the knowledge sources provided do not contain any information about the "better-auth" library or about mutating the request body before passing it to a function like toWebRequest in a Nuxt server handler. The sources do explain how to read and validate the request body using readBody or readValidatedBody, and how to handle errors or modify responses, but they do not cover patching or replacing the body on the event object itself, nor do they discuss creating a new event for downstream handlers. If you need to modify the body before passing it to another handler, you would typically read the body, modify it, and then pass the modified data directly to the downstream function if it supports receiving the body as an argument. However, if the downstream function expects the original event object and reads the body itself, there is no documented way in the provided sources to overwrite or patch the body on the event object in Nuxt. If you have control over the downstream handler, you might consider refactoring it to accept the body as an argument, or you could wrap the handler to inject your modifications. But again, the knowledge sources do not provide explicit guidance or examples for this scenario. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai•3w ago
<@693201794137981049> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
lazygopher
lazygopherOP•3w ago
@kapa.ai ok I have made some progress, but after successful registration the next call to /api/auth/get-session returns null 
export default defineEventHandler(async (event) => {
    const body = await readBody(event)
    const modifiedBody = {
        ...body,
        image: `...`,
    }

    return await auth.api.signUpEmail({
        body: modifiedBody,
    })
})
export default defineEventHandler(async (event) => {
    const body = await readBody(event)
    const modifiedBody = {
        ...body,
        image: `...`,
    }

    return await auth.api.signUpEmail({
        body: modifiedBody,
    })
})
I get the same response as the previous handler. But follow up api call to get-session
kapa.ai
kapa.ai•3w ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the knowledge sources provided, there is no explicit information about the "better-auth" library or its integration with Nuxt, nor about the specific behavior of session management after registration with a custom auth handler. However, I can share some general Nuxt session/auth troubleshooting steps that are relevant: 1. Session Cookie Handling:
In Nuxt, session data is often stored in cookies. If your registration endpoint does not set the session cookie correctly, or if the client does not receive or send it on subsequent requests, the /api/auth/get-session endpoint will return null. Make sure your registration handler sets the session cookie, and that the client includes it in future requests. This is a common pattern in Nuxt authentication flows, as seen in the Nuxt Auth Utils recipe. 2. API Route Consistency:
After a successful registration, you may need to refresh the session on the client side. For example, in the Nuxt Auth Utils example, after login, the session is refreshed using a composable before redirecting the user: 
   await refreshSession()
   await navigateTo('/')
   
   await refreshSession()
   await navigateTo('/')
This ensures the client has the latest session data before making further API calls. If you skip this step, the session may appear as null until the client reloads or refreshes the session manually. 3. Server-Side Session Storage:
If your auth library or handler does not persist the session server-side (e.g., in a cookie or database), the session will not be available for subsequent requests. Ensure your handler is correctly setting the session after registration, similar to how setUserSession is used in the Nuxt Auth Utils example: 
   await setUserSession(event, { user: { ... } })
   
   await setUserSession(event, { user: { ... } })
4. Check for SSR/CSR Issues:
Sometimes, session issues arise due to differences between server-side and client-side rendering. Make sure your session logic is compatible with both environments, as described in the Nuxt session/auth documentation. Summary:
The knowledge sources do not contain enough information about "better-auth" or your specific handler, but based on Nuxt best practices, check that your registration handler sets the session cookie, and that the client refreshes the session after registration. If you are using a custom auth library, ensure it integrates with Nuxt's session management as expected. If you can share more details about how your session is set after registration, or how your /api/auth/get-session endpoint is implemented, I may be able to provide more targeted advice. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai•3w ago
<@693201794137981049> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

Did you find this page helpful?