npm

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

My Next.js app called a Netlify Function through netlify dev, and the function ran but event.body was always undefined. The exact same function deployed to Netlify parsed the body correctly. The thread is from December 2022. A maintainer po

supporting2026-09-23 22:29 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

My Next.js 13 project uses the Notion client and builds fine locally, but the Vercel deployment fails with: `Module not found: Can't resolve 'encoding' in '.../node_modules/node-fetch/lib'`. I am on Notion SDK 2.2.2 with Node 16/18. Did Nex

incidental2026-09-23 21:41 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

Upgrading an Angular app from @okta/okta-auth-js 6.2.0 to 6.4.0 produced Unhandled Promise rejection: Failed to execute 'postMessage' on 'BroadcastChannel': Channel is closed during npm test (and in the console at runtime). The SDK's cross-

incidental2026-09-23 16:02 UTC

After updating to @perplexity-ai/mcp-server 0.14.0, Claude Code fails at startup with: tools.70.custom.input_schema: input_schema does not support oneOf, allOf, or anyOf at the top level. Version 0.2.2 worked fine. Downgrading is not really

supporting2026-09-23 15:38 UTC

On a headless server over SSH, `npm run dev` in the Convex Next.js template fails during the `predev` script at the `convex dashboard` step with `Error: spawn xdg-open ENOENT`. The CLI tries to open the dashboard URL in the default browser,

supporting2026-09-23 13:31 UTC

Every cdktf-cli command suddenly started failing with Error: ENOENT: no such file or directory, scandir '.../node_modules/@cdktf/cli-core/templates', on both CI and local machines, with no changes to any infrastructure code. The breakage st

incidental2026-09-23 13:28 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

After upgrading from 15.5.3 to 16.0.0, npm run dev fails with a build error on a .module.scss file: Error: Can't find stylesheet to import, pointing at a bare @use "variables" as *; line. Their next.config.ts used sassOptions with includePa

supporting2026-09-23 01:11 UTC

A multi-client CLI release has exact candidate bytes, a verified backend, and successful native acceptance for Codex and Cursor. One retained Claude workflow repeatedly produces a substantive prose answer but never invokes the automatic tas

primary2026-09-18 20:56 UTC

Question: when a single release script already runs readiness checks, a full test gate, packaging of an npm tarball, a candidate backend deployment, native coding-client acceptance, npm publication under a staging dist-tag, a signed release

primary2026-09-18 17:41 UTC