tool · inferred from evidence
npm
Package manager for Node.js, referenced as the source of the tarball with the shebang issue.
- Firebase CLI: "firebase.ps1 cannot be loaded because running scripts is disabled on this system"
After npm i -g firebase-tools on Windows, running firebase in the VS Code PowerShell terminal failed with: firebase : File [npm global bin]\firebase.ps1 cannot be loaded because running scripts is disabled on this system. The same commands
- 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
- Notion SDK breaks Next.js 13 Vercel build: `Module not found: Can't resolve 'encoding'`
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
- Perplexity MCP npx wrapper causes EOF errors in strict MCP clients
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
- 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,
- All cdktf-cli commands fail with ENOENT no such file or directory, cli-core/templates (0.17.2)
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
- sync-wasm connect() fails with "unexpected path ... .db-log: files must be created in advance for OPFS IO"
In `@tursodatabase/sync-wasm`, calling `connect()` against a hosted Turso database that negotiates MVCC sync rejects before any application SQL runs: `Internal error: unexpected path fresh-[random-id].db-log: files must be created in advanc
- Observable Framework npm run dev fails with listen EINVAL on Fedora
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
- 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
- Browserless v2 SDK docker image: Couldn't load route "/chrome/content" due to missing browser binary for...
Built a custom Browserless image with the v2 SDK (`npx @browserless.io/browserless create`, then `npm run docker`). On ARM64 the container starts but every Chrome route fails with: `Couldn't load route "/chrome/content?(/)" due to missing b
- Fix reserved keyword 'package' bundling error in flutterwave-node-v3
Bundling flutterwave-node-v3 with rollup fails with a SyntaxError because the package used JavaScript reserved words like package as variable names. A maintainer confirmed the reserved-word usage was removed from the library. Bump flutterwa
- subscribeToContentCardsUpdates not firing in Next.js (Braze web SDK)
On Next.js with Braze Web SDK 4.1.0 installed via npm, `subscribeToContentCardsUpdates((cards) => ...)` never fires after `initialize()` succeeds. The reporter expected existing Content Cards to appear on login and new cards to arrive while
- Cloudinary: uploading file as buffer fails in production (Next.js)
In a Next.js application using the Cloudinary NPM SDK, uploading a file as a byteArrayBuffer works when the server runs in development but throws an error in production (after npm run build and npm start). The failure came from how upload_s
- SandboxError "Invalid redirect value, must be one of follow or manual" running E2B on Vercel Edge
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
- Fix 'Error: Public Key required' when running flutterwave-node-v3 tests
The flutterwave-node-v3 test suite fails at startup with `Error: Public Key required` from rave.base, before any test runs. The constructor validates credentials, so the suite needs a test PUBLIC_KEY and SECRET_KEY available when the Rave c
- Fix Flutterwave Node v3 Transaction.verify failing
Calling flw.Transaction.verify on flutterwave-node-v3 fails even with valid credentials, which looks like the module's base URL not being wired up. A maintainer confirmed the verify path was broken and fixed in the latest release. Update th