platform · inferred from evidence
Node
A JavaScript runtime environment.
- TelnyxWebhook.verify() throws TypeError: Cannot read properties of undefined (reading 'detached') in ESM
In an ESM project, calling `TelnyxWebhook.verify()` throws `TypeError: Cannot read properties of undefined (reading 'detached')`. The SDK's ESM build imports tweetnacl with `import * as nacl from 'tweetnacl'`, but tweetnacl is a CommonJS-on
- Nx 21.4.0: node processes linger at 100% CPU after ending the session
On Nx 21.4.0, after shutting down the dev stack, node processes linger and keep consuming 100% CPU; nx reset --only-daemon kills some but not all of them. Over a day of up/down cycles this leaves multiple node processes spinning and grinds
- Renovate process never exits since 24.40.0 in Kubernetes
Starting with Renovate 24.40.0, the renovate process finishes its work but never exits, hanging the Kubernetes cronjob pod. The cause was the AWS SDK ECR client keeping a connection open, so the node process stayed alive.
- Logto fails to start: self signed certificate in certificate chain (managed Postgres)
Starting the Logto container against a DigitalOcean Managed Postgres database failed during initialization with Error: self signed certificate in certificate chain. DigitalOcean's managed databases present a certificate chain Node does not
- Error: Cannot find module '.prisma/client/default' on startup (Prisma 7, custom output path)
On app startup, Node crashes with Error: Cannot find module '.prisma/client/default' (require stack points at node_modules/@prisma/client/default.js) before any database connection is attempted. The setup used provider = "prisma-client" wit
- Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' (MODULE_NOT_FOUND)
Deploying a Prisma 6/7 app fails at runtime with Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' (code MODULE_NOT_FOUND) even though it works locally. Reported on Vercel and in Docker. Two distinct causes surfa
- TypeError: e._formData.get is not a function when calling a Server Action in Next.js
Calling a server action from a client component throws TypeError: e._formData.get is not a function. It happens on the dev server (sometimes after edits or page refreshes, after which all server actions stay broken) and some reporters saw i