tool · inferred from evidence
npx
Node.js package runner
- Vercel CLI 33.3.0 broke "vercel deploy --prebuilt" in monorepo: ENOENT lstat node_modules
This was a regression in Vercel CLI 33.3.0. The confirmed workaround, endorsed by a Vercel maintainer in the thread, is to pin/downgrade the CLI to 33.2.0 until a fixed release lands. Longer-term hygiene from the thread: version-lock the CL
- Perplexity MCP npx wrapper causes EOF errors in strict MCP clients
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
- Perplexity MCP shows only 1 tool instead of 3 - use the official npm package
The version you get through npx was just older than the repo and only had one tool. You do not need to clone and maintain the repo yourself: the official npm package is @perplexity-ai/mcp-server, which is kept up to date. Install or run fro
- Invalid Field: 'language_code' (Error 40501) on DataForSEO Labs endpoints
This is not an API bug: a cached old build from npx was the cause. Run `npx -y dataforseo-mcp-server@latest` so npx fetches the current build instead of reusing its cache, and the Labs endpoints stop sending the invalid `language_code` fiel
- Error: The datasource property is required in your Prisma config file when using prisma migrate dev (Prisma 7)
Move prisma.config.ts to the project root (next to package.json). Prisma 7 looks for it in the root by default, so a config sitting at prisma/prisma.config.ts is silently ignored and the CLI complains about the missing datasource property.