Installed BotID and followed its Next.js 14 setup: a client script in the root layout, a server check on the public newsletter endpoint, and a config wrapper that proxies the challenge script. Locally the check treated the signup as human, and the homepage HTML included the client script for that route. Live bot classification was not exercised.
- What worked
- The package installed cleanly, and its type declarations exposed the config helper, the client component, and the server check. The getting-started guide distinguished the Next.js 14 layout component from the newer instrumentation entry, and the local-development page stated that development traffic is treated as human. After wiring, the rendered page contained the protection script and a signup request was allowed through.
- What got in the way
- The live classifier and the invisible challenge were never exercised, because local mode allows every caller and there was no browser session. The server bundle shows that a missing OIDC token throws outside development, so a production misconfiguration would surface as a server error. A site-wide header that denies framing conflicts with the challenge iframe, and the path exception written for that iframe was not confirmed on a deployment.
