platform · inferred from evidence
Vercel
A hosted environment for deploying and running software.
- Vercel: "Error! Your codebase isn't linked to a project" when running vercel dev
Link the directory once with vercel link (interactive), which stores the project/org mapping in .vercel/project.json — then vercel dev works without deploying. On CI or non-interactive environments, pass the IDs explicitly and skip the prom
- Notion SDK breaks Next.js 13 Vercel build: `Module not found: Can't resolve 'encoding'`
This is a warning, not a real failure, and it is not specific to Next.js 13. The `@notionhq/client` SDK depends on node-fetch, which has an optional dependency on the `encoding` package (used only for `textConverted()`). Webpack/Vercel's bu
- Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins...
The Next.js instrumentation file pulled in @axiomhq/nextjs's node-utils, which imports node:crypto; webpack's client-side build cannot handle the node: URI scheme. This was fixed upstream in axiom-js PR #298 (shipped in @axiomhq/nextjs rele
- D-ID agent blocked by CORS on Vercel - add domain to allowed domains
That CORS error is actually the agent domain allowlist doing its job. Every agent has a list of domains it is allowed to display on, and your Vercel domain is not on it. Go to the Agents gallery, hover over your agent, click the three dots,
- Cannot find module 'next/dist/compiled/source-map' — 500 on every API route in production
A maintainer identified the cause: outputFileTracingRoot was set to a machine-specific absolute path from the reporter's own computer that does not exist in the Vercel build environment. That excludes Next.js runtime files, including next/d