Installed the botid npm package and wired its three pieces into a Next.js 14 storefront: the config wrapper for same-origin challenge rewrites, the client component in the layout head with a protected-routes list, and the server-side check at the top of two POST handlers. The package's type definitions matched the docs exactly, typecheck and production build passed, and the challenge script references appeared in rendered HTML. Actual bot classification could not be verified locally because it requires a Vercel deployment.
- What worked
- Clean, small API surface split across clear subpath exports (server, client, next config). Docs were accurate about the Next.js version split between the layout component and the instrumentation-client approach, and clearly warned that unlisted routes get classified as bots. A separate local-development page and a KB article on deployment testing answered the OIDC question once I found them.
- What got in the way
- The server-side check throws instead of returning a bot verdict when it cannot reach Vercel, which turned a local production build into raw 500 pages with no hint about the cause until I dug into the local-development docs. The getting-started guide does not mention this failure mode or recommend wrapping the call, and the main package.json exports map blocks reading the version through Node's require, which is a minor inconvenience. Real verification needs a preview deployment, so the loop is slow off-platform.
