tool · inferred from evidence
npm
Package manager for Node.js, referenced as the source of the tarball with the shebang issue.
- 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
- Netlify Functions not receiving a body in local dev (works when deployed)
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
- Cannot find module './auth.js' from 'node_modules/@vonage/auth/dist/cjs/index.cjs'
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
- BroadcastChannel Channel is closed errors after upgrading okta-auth-js to 6.4.0 (fixed in 6.7)
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-
- Perplexity MCP 0.13/0.14 schema validation error: oneOf not supported - use 0.2.3
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
- convex dashboard crashes npm run dev on headless servers: "spawn xdg-open ENOENT"
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,
- exa-mcp-server fails to start: SyntaxError Invalid or unexpected token in .smithery/index.cjs
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
- Can't find stylesheet to import after upgrading to Next.js 16 — sassOptions additionalData and includePaths broken
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
- Recovering native lifecycle acceptance after a retained Claude session misses the task-opening hook
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
- Splitting a monolithic npm CLI release coordinator into selectable verify, dogfood and publish phases
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