2 replies

Database Error in Email Signin API

Database related

Next.js🤔QuestionOAuth related

I'm just trying to get started with Better Auth in my Nextjs app, and have been trying to piece together a working auth system based on official guides that seem to have some errors. I've ended up with an attempt at Nextjs proxy based auth, and this only has one route to protect:

matcher: ["/productAdmin"]

matcher: ["/productAdmin"]

.

I'm using Prisma ORM with a Postgres db, with plain

emailAndPassword

emailAndPassword

auth, and have added a signup route and form, which seems to be working. When I submit, my new account and user are added to the db.

My problem arises as soon as I include a call to

auth.api.signInEmail

auth.api.signInEmail

in my login server action, which is almost a duplicate of my

signup

signup

server action, even without clicking the Login button on my Login form. The form is client side, but included in the server side

LoginPage

LoginPage

on my

login

login

route. It seems like the login action is being called because somehow all routes are being protected.

The actual error is a build error in

node_modules/.pnpm/pg@8.16.3/node_modules/pg/lib/connection-parameters.js

node_modules/.pnpm/pg@8.16.3/node_modules/pg/lib/connection-parameters.js

Module not found: Can't resolve 'dns'
  1 | 'use strict'
  2 |
> 3 | const dns = require('dns')
    |             ^^^^^^^^^^^^^^
  4 |
  5 | const defaults = require('./defaults')
  6 |

Module not found: Can't resolve 'dns'
  1 | 'use strict'
  2 |
> 3 | const dns = require('dns')
    |             ^^^^^^^^^^^^^^
  4 |
  5 | const defaults = require('./defaults')
  6 |

Yet my

signin

signin

action that seems to be using the same db is working.

I haven't included anything yet becuase there is so much, so I'm hoping someone willing to assist might recognise a similar scenario and tell me what to share.

Better Auth•4w ago•

2 replies

VoidPointer

Database Error in Email Signin API

Database related

Next.js🤔QuestionOAuth related

matcher: ["/productAdmin"]

matcher: ["/productAdmin"]

.

I'm using Prisma ORM with a Postgres db, with plain

emailAndPassword

emailAndPassword

auth, and have added a signup route and form, which seems to be working. When I submit, my new account and user are added to the db.

My problem arises as soon as I include a call to

auth.api.signInEmail

auth.api.signInEmail

in my login server action, which is almost a duplicate of my

signup

signup

server action, even without clicking the Login button on my Login form. The form is client side, but included in the server side

LoginPage

LoginPage

on my

login

login

route. It seems like the login action is being called because somehow all routes are being protected.

The actual error is a build error in

node_modules/.pnpm/pg@8.16.3/node_modules/pg/lib/connection-parameters.js

node_modules/.pnpm/pg@8.16.3/node_modules/pg/lib/connection-parameters.js

Module not found: Can't resolve 'dns'
  1 | 'use strict'
  2 |
> 3 | const dns = require('dns')
    |             ^^^^^^^^^^^^^^
  4 |
  5 | const defaults = require('./defaults')
  6 |

Module not found: Can't resolve 'dns'
  1 | 'use strict'
  2 |
> 3 | const dns = require('dns')
    |             ^^^^^^^^^^^^^^
  4 |
  5 | const defaults = require('./defaults')
  6 |

Yet my

signin

signin

Database Error in Email Signin API

Similar Threads

Database Error in Email Signin API

Similar Threads

Similar Threads

Similar Threads