fix(douyin): handle missing passport csrf cookie

[haix8]

Summary

• remove the obsolete login_guiding_strategy cookie bootstrap request
• send a non-empty random passport_csrf_token for the Douyin hot-list request
• validate Douyin status_code and reject missing or empty word_list responses

Why

Douyin no longer returns passport_csrf_token from the login-guiding endpoint. The existing regex therefore returns null and logs:

TypeError: Cannot read properties of null (reading '1')

The hot-list endpoint currently requires a non-empty passport_csrf_token cookie but does not require the value to come from that obsolete endpoint.

Verification

• pnpm exec eslint src/routes/douyin.ts
• pnpm exec prettier --check src/routes/douyin.ts
• pnpm run build
• fresh /douyin?cache=false: HTTP 200, 50 items, fromCache=false
• cached /douyin: HTTP 200, 50 items, fromCache=true

[gemini-code-assist]

Code Review

This pull request refactors the Douyin route by replacing the temporary cookie fetching logic with a randomly generated UUID for the passport_csrf_token cookie, and adds validation for the API response structure and status code. The review feedback suggests using the globally available Web API crypto.randomUUID() instead of importing from node:crypto to ensure compatibility with edge runtimes, and recommends explicitly checking for a null or undefined responseData first to simplify the error handling and avoid repetitive optional chaining.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Checking responseData for null/undefined first is safer and provides a cleaner error message. If responseData is null or undefined, evaluating responseData?.status_code !== 0 will result in true (since undefined !== 0), which then throws an error with status_code=undefined. Explicitly checking !responseData first avoids this and allows us to remove the repetitive optional chaining.

  const responseData = result.data;
  if (!responseData) {
    throw new Error("获取抖音热榜失败: 响应数据为空");
  }
  if (responseData.status_code !== 0) {
    const reason = responseData.status_msg || "status_code=" + responseData.status_code;
    throw new Error("获取抖音热榜失败: " + reason);
  }
  const list = responseData.data?.word_list;
  if (!Array.isArray(list) || list.length === 0) {
    throw new Error("获取抖音热榜失败: word_list 缺失或为空");
  }

[gemini-code-assist]

Since this project uses Hono, it is highly likely to be deployed on edge runtimes like Cloudflare Workers, where node:crypto is not available by default (unless Node.js compatibility is explicitly enabled). Using the standard Web API crypto.randomUUID() (which is globally available in modern Node.js, Cloudflare Workers, Deno, and Bun) improves cross-runtime compatibility. You can remove the import { randomUUID } from "node:crypto"; on line 4 and use crypto.randomUUID() directly here.

Suggested change

	Cookie: `passport_csrf_token=${randomUUID()}`,
	Cookie: "passport_csrf_token=" + crypto.randomUUID(),