-
Notifications
You must be signed in to change notification settings - Fork 4
TypeError: Cannot read properties of undefined (reading 'replace') #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey 👋 Can you paste your |
Hi @igalklebanov , sorry but I already migrated out of nextjs. |
Hey, @igalklebanov I have the same error as op
package.json
|
Exactly same issue, while default pg dialect works as should. |
Hey 👋 This has |
same problem next 12.3.4 or next 14 |
I got the same problem as well, here's the error it gives
Here's the deps version I'm using
This project is purely express running on Node 20 on docker container in a kubernetes cluster. |
This seems related to Try using your |
Closing this. Tests are passing with Node LTS, postgres@latest, kysely@latest. https://github.com/kysely-org/kysely-postgres-js/actions/runs/8107957535 Was able to reproduce the same exception when docker container was down or by passing a wrong Not related to Kysely or kysely-postgres-js. |
I guess it unrelated to this adapter but host is valid because it works for some time and than nextjs hot reload crashes it and after server restart it works again |
I can confirm that this is related to a malformed URL. In my case I had a |
Yeah maybe but i use credentials not url and error still happens |
I remove |
For those who have this problem still unresolved - in my case I forgot to destroy db instance after each call, so requests were creating a new clients each time. Once max client threshold was reached it failed with this ugly error:
|
Same as with this issue: #9
I'm using latest of everything and this is on nextjs 14, node 20.
I tried to understand the problem but I failed to do so.
I rolled back to
pg
and worked fine, therefore I think it's eitherpostgres
or this adapter.The text was updated successfully, but these errors were encountered: