Two related changes around datacenter-IP deployments:
- New optional 'fetch' field on Options. getSubtitles and getVideoDetails
now accept a custom fetch implementation, so users deploying to Vercel,
AWS Lambda, or Cloudflare Workers can route requests through a
residential proxy (undici ProxyAgent, etc.) to bypass YouTube's bot
challenge. Defaults to global fetch — fully backward compatible.
- README now accurately describes which environments work. The previous
copy claimed Vercel / AWS Lambda / Edge Runtime were fully supported.
That hasn't been true since YouTube rolled out aggressive datacenter-IP
filtering in 2024 — most deployments hit "Sign in to confirm you're
not a bot". Replaced the misleading section with a real environment
table and a worked example of the proxy pattern.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>