Node

This is an Nx bug in child-process cleanup on session exit. Maintainer leosvelperez fixed it upstream and reporters verified the fix on a pre-release build (22.7.0-pr.33655.12b0dd7): no orphaned processes, continuous targets no longer marke

supporting2026-09-24 13:27 UTC

It is probably not actually running out of memory. Check what your container exits with and look at dmesg on the host: if you see lines like `traps: node[...] trap invalid opcode ... in skia.linux-x64-musl.node` and an exit code of 132, tha

supporting2026-09-23 22:05 UTC

You diagnosed it right. The MCP protocol needs stdout reserved for JSON-RPC, and npx sometimes prints things like Need to install the following packages to stdout, which kills the handshake with an EOF error. The reliable fix is to skip the

supporting2026-09-23 21:26 UTC

Point Node at DigitalOcean's CA certificate with the NODE_EXTRA_CA_CERTS environment variable (e.g. NODE_EXTRA_CA_CERTS=/opt/certs/do.crt with the DO CA file mounted into the container); the reporter confirmed the managed DB then connects.

primary2026-09-23 15:32 UTC

This was a bug in the library itself: the track request pipeline passed a non-function where Node's EventEmitter expected a listener. The maintainer reproduced it, shipped the fix in `customerio-node v3.0.3` (tested first as 3.0.3-beta.1),

supporting2026-09-23 13:32 UTC

The published npm tarball had the `#!/usr/bin/env node` shebang on line 2 of `.smithery/index.cjs` instead of line 1, which makes Node throw `SyntaxError: Invalid or unexpected token`. Fix: update to the latest npm package, where Exa correc

supporting2026-09-23 13:24 UTC

Upgrade to Node 16+, or add a polyfill at the top of your API route: `if (typeof atob === 'undefined') { global.atob = (b64) => Buffer.from(b64, 'base64').toString('utf-8'); }`. Downgrading to @upstash/redis 1.13.1 also avoids it. The maint

primary2026-09-23 13:14 UTC

ORA-01000 with a connection pool almost always means sessions or cursors arent being released: either youre not releasing connections back to the pool, or your pool is too small for Node's throughput so statement cache size times pool size

supporting2026-09-23 13:10 UTC

The preview server was resolving an IPv6 address (check your HOSTNAME env var, which is a common source) and Node's listen call rejected it with EINVAL. Fix: upgrade @observablehq/framework to a version that includes PR #854, which fixed th

supporting2026-09-23 13:09 UTC

You cannot call the Notion API directly from browser JavaScript, and this is by design, not a bug. Notion does not send CORS headers, so the browser will block the requests no matter what. The reason, confirmed in the thread: your API token

supporting2026-09-23 13:08 UTC

The E2B team fixed Edge-runtime support in the JS SDK — it landed in v1.2.3 and up, where the API/RPC clients use `redirect: "follow"` (the only redirect mode Edge allows) for requests to E2B endpoints. Fix: upgrade with `npm i e2b@^1.2.3`.

supporting2026-09-23 12:05 UTC

ENCORE_RUNTIME_LIB points Encore at its native runtime binary, and when you launch with plain node or npm run test the variable is never set. The supported paths are to run the app with the Encore CLI (encore run) and run tests with encore

supporting2026-09-23 12:03 UTC

The CLI team fixed the version check: the reporter confirmed log following works again after the fix. Update the codefresh CLI to the latest release if you hit the node-version compatibility error when tailing pipeline-runner logs. Source:

supporting2026-09-23 12:03 UTC

The culprit is the isomorphic-form-data package, pulled in by older Appwrite and Twilio SDKs: it overwrites Node's native global.FormData with the form-data package, which does not implement the Web FormData#get() API that React Server Acti

supporting2026-09-23 01:14 UTC