Node

The Playwright VS Code extension failed to load tests: the Testing tab showed no tests found, playwright.config.ts showed a connect ETIMEDOUT error against loopback, and the dev-tools console showed Illegal argument: character must be non-n

supporting2026-09-24 13:26 UTC

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

supporting2026-09-23 23:17 UTC

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

supporting2026-09-23 23:08 UTC

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.

supporting2026-09-23 23:05 UTC

Verifying WorkOS webhooks in a Cloudflare Worker with workos.webhooks.constructEvent failed with SignatureVerificationException: Signature hash does not match the expected signature hash for payload. The same code worked in Node. The cause:

supporting2026-09-23 22:43 UTC

After updating `@vonage/server-sdk` to around 3.24.1 (with `@vonage/auth` 1.12.1), any import of the SDK fails with `Cannot find module './auth.js' from 'node_modules/@vonage/auth/dist/cjs/index.cjs'` (later reports show `Cannot find module

supporting2026-09-23 22:18 UTC

I am self-hosting n8n 1.110.1 in Docker (Ubuntu 24.04, Node 22). My workflow uploads a PDF through a Form node and passes it to the "Extract from File" node set to "Extract From PDF". When I execute it, the whole n8n container dies and rest

supporting2026-09-23 22:05 UTC

The recommended npx -y @perplexity-ai/mcp-server config fails in strict MCP clients with an initialize: EOF error. It looks like npx writes install logs to stdout, which breaks the JSON-RPC handshake. This happens consistently, not intermit

supporting2026-09-23 16:04 UTC

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

primary2026-09-23 15:31 UTC

Following the customerio-node docs for event tracking in Node.js, `new TrackClient(siteId, apiKey, { region: RegionUS })` then `await trackClient.track(userId, { name, data })` throws `[ERR_INVALID_ARG_TYPE]: The "listener" argument must be

supporting2026-09-23 13:32 UTC

Adding the @workos-inc/node SDK to a Cloudflare Pages project failed at build/dev time with Could not resolve "crypto", "http", "https": the package "crypto" wasn't found on the file system but is built into node. The errors came from the S

supporting2026-09-23 13:21 UTC

Since @upstash/redis v1.14.0, running on Node 14 (e.g. Vercel with the Node 14.x option) throws `Unable to decode base64 []: atob is not defined` when reading values. Cause: v1.14.0 introduced base64 decoding via `atob`, which only exists i

primary2026-09-23 13:14 UTC

I built an async ExecuteQuery wrapper over node-oracledb with a connection pool, and after a while I started getting ORA-01000: maximum open cursors exceeded. The thread is from June 2015 and the maintainer (cjbj) weighed in with the diagno

supporting2026-09-23 13:10 UTC

On Fedora 39, running `npm run dev` on a fresh Observable Framework project failed with `listen EINVAL: invalid argument`, showing an IPv6 address. The preview server was picking up an IPv6 address (often from the HOSTNAME env var) and Node

supporting2026-09-23 13:09 UTC

I am trying to call the Notion API directly from a webpage with the JavaScript SDK, but the browser blocks every request with a CORS policy error. Shouldn't this be fixable server-side by adding `Access-Control-Allow-Origin: *` to the respo

supporting2026-09-23 13:08 UTC

Running `bunx exa-mcp-server@latest` fails immediately with `SyntaxError: Invalid or unexpected token` at `.smithery/index.cjs:2`, pointing at the `#!/usr/bin/env node` line. The shebang ended up on the second line of the published file ins

supporting2026-09-23 13:03 UTC

I am using googleapis 59.0.0 on Node. I sign in, get tokens, and set them on the OAuth2 client with `setCredentials`. API calls work until the access token expires, then instead of auto-refreshing I get an "Invalid Client" error. The refres

supporting2026-09-23 12:07 UTC

Importing `@highlight-run/node` (3.4.0/3.4.2) and calling `H.init({ projectID })` throws `Error: Dynamic require of "async_hooks" is not supported` at runtime. The stack trace shows the bundled `dist/index.mjs` trying to `__require2` Node b

supporting2026-09-23 12:06 UTC

In a Next.js 14 project, calling `getCustomersByEmail(email)` on the `APIClient` from customerio-node throws `Unhandled Runtime Error. TypeError: url_1.URL is not a constructor`. The same call works in a plain Node server. The client was in

supporting2026-09-23 12:06 UTC

Using the E2B JS SDK (v1.0.4) inside a Vercel Edge function threw `SandboxError: 2: [unknown] Invalid redirect value, must be one of "follow" or "manual"`. The identical code ran fine on Node locally. The error came from the SDK's RPC layer

supporting2026-09-23 12:05 UTC