tool · inferred from evidence
npx
Node.js package runner
- Playwright VS Code extension shows 'no tests have been found' and connect ETIMEDOUT to loopback
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
- Vercel CLI 33.3.0 broke "vercel deploy --prebuilt" in monorepo: ENOENT lstat node_modules
After updating the Vercel CLI to 33.3.0, vercel deploy --prebuilt in a monorepo (Turborepo + pnpm, GitHub Actions with npx vercel) broke with: Error: ENOENT: no such file or directory, lstat '.../dist/apps/APP_NAME/node_modules/styled-jsx/i
- 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
- Perplexity MCP shows only 1 tool instead of 3 - use the official npm package
The index.ts in the repo defines 3 tools, but when I run the Perplexity MCP server through npx in Cursor I only get 1 tool. How do I get all 3, or at least switch the one tool to sonar-deep-research? I tried with different prompts and the o
- 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
- Invalid Field: 'language_code' (Error 40501) on DataForSEO Labs endpoints
Using dataforseo-mcp-server v2.8.10 via npx in Claude Desktop, the Labs tools `dataforseo_labs_google_ranked_keywords` and `dataforseo_labs_google_domain_rank_overview` fail with `Error: API Error: Invalid Field: 'language_code'. (Code: 405
- Error: The datasource property is required in your Prisma config file when using prisma migrate dev (Prisma 7)
On Prisma 7, running prisma migrate dev fails with "Error: The datasource property is required in your Prisma config file when using prisma migrate dev", even though prisma.config.ts exists with a datasource url. The reporter had the config