tool · inferred from evidence
npm
Package manager for Node.js, referenced as the source of the tarball with the shebang issue.
- Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './server/stdio.js' is not defined by "exports" (ClickUp MCP)
Fixes the ClickUp MCP server crashing on startup with an exports error on old Node. Use when the error names server/stdio.js and exports. Not for token or schema issues.
- dd-trace for Node: npm install dd-trace, require and init it before any app code
Node APM with dd-trace: npm install dd-trace, then require and init the tracer before any other import. Initialization order is the classic failure. Not the full reference manual.
- Build Fails Due to “Failed to Resolve Version 1 of Yarn” Without Any Config Changes
Railpack: build Fails Due to “Failed to Resolve Version 1 of Yarn” Without Any Config Changes. The verified fix is Fix: Maintainer iloveitaly (maintains railpack): this was platform-side, the mise yarn backend (asdf) was broken/corrupted fo
- Tenant config as code: auth0-deploy-cli and the Terraform provider
Click-ops tenants drift. The deploy CLI exports tenant config to a local repo so changes are reviewed, diffed, and replayable across tenants and environments. Not the full reference manual.
- Multiple shebang lines in .smithery/index.cjs breaks stdio transport
Exa MCP Server: multiple shebang lines in .smithery/index.cjs breaks stdio transport. The verified fix is Fix: Collaborator theishangoswami: the broken npm build was fixed; exa-mcp-server@3.0.5 works. Use this when you hit the symptoms abov
- Add custom claims with a post-login Action: namespace, setCustomClaim, deploy
Custom claims need a namespaced name, the right token target, and three steps people skip: deploy the Action, attach it to the login flow, and test with a fresh login. Not the full reference manual.
- Nx daemon unsupported in WebAssembly: missing OS-specific optional packages
Shows how to fix nx daemon unsupported in WebAssembly: missing OS-specific optional packages. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
- chargebee: Can't resolve 'http' after upgrading to Next.js 15 (fixed in v3.12.0)
Fixes the chargebee Node SDK failing with 'Can't resolve http' after upgrading to Next.js 15. Use this when the build breaks on browser/edge bundling of Node core modules. Not for other missing modules.
- Railway/cli:5.0.0 and onwards broke RAILWAY_TOKEN deployments
CLI: railway/cli:5.0.0 and onwards broke RAILWAY_TOKEN deployments. The verified fix is Fix: Takeaway for agents: pin the CLI version in CI (`npm install -g @railway/cli@5.2.0` / pin the docker tag) instead of `latest` so a bad release can'
- Send email with SendGrid from Node.js (@sendgrid/mail v8)
The exact working pattern for @sendgrid/mail: setApiKey from the environment, a plain message object, and how to unwrap the response array and the error body when a send fails. Not the full reference manual.
- strcpy_chk: symbol not found
Libsql Client Ts: strcpy_chk: symbol not found. The verified fix is Fixed via tursodatabase/libsql#1724, released in libsql v0.4.3 - `npm update` picks it up. Use this when you hit the symptoms above in libsql-client-ts; not for unrelated l
- npm error could not determine executable to run (exa-mcp-server)
Fixes the exa-mcp-server install failure where npx reports it cannot determine an executable to run. Use when the Exa MCP server will not start locally and the npx command exits with the executable-resolution error. Not for missing API key
- Failed to execute 'subscribe' on 'PushManager': Subscription failed - no active Service Worker
Fixes 'Failed to execute subscribe on PushManager: Subscription failed - no active Service Worker' from Firebase messaging getToken by upgrading the Firebase JS SDK to 11.1.0 or later. Use when getToken intermittently throws this in Next.js
- Mcp server only has two entry points now missing linkedin, deepresearch etc
Restores missing exa-mcp-server tools (linkedin search, deep researcher, crawling, company research) by upgrading to 3.0.8/3.0.9 and using the new single-dash tools= flag syntax. Use when only web_search_exa and get_code_context_exa appear
- SandboxError "Invalid redirect value, must be one of follow or manual" running E2B on Vercel Edge
Fixes the E2B SandboxError "Invalid redirect value, must be one of follow or manual" on Vercel Edge by upgrading the E2B JS SDK to v1.2.3 or newer, where the RPC layer uses redirect: "follow". Use when E2B sandbox calls fail inside Vercel E