cult-ui answers 200 again: re-verify #31's known issue and `manual_fetch_only`

未關閉
#91 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
54/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
javascript, node.js, react, tailwindcss
領域
frontend, tooling

研究方向

Start with scripts/health-check.py and fetch-showpieces.mjs, then inspect the known_issues[] record and manual_fetch_only flags for cult-ui. Verify npx shadcn@latest add from more than one network and inspect whether the response body is registry JSON. Done when the record, flags, and static preview are removed, or #31 has a dated comment confirming the challenge still affects real installs.

由索引模型根據 Issue 內容生成。

描述

bug scripts

A local scripts/health-check.py run on 2026-11-05 got 79/79 targets ok, including all seven cult-ui targets that the last committed report listed as challenged (Vercel Attack Challenge Mode, #31).

The gallery build still skips texture-card without trying, because fetch-showpieces.mjs treats any host in known_issues[] as blocked, and all six cult-ui entries stay manual_fetch_only.

Check from more than one network that npx shadcn@latest add actually installs a cult-ui item (a 200 on HEAD is not proof the body is registry JSON).

Done when: either the known_issues[] record, the manual_fetch_only flags, and the static texture-card preview are removed, or #31 gets a dated comment saying the challenge is still on for real installs.

主要語言
JavaScript
星號
17
分支
7
PR 合併指標
30 天內沒有已合併 PR

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CreativesLibrary/Components 的其他 Issue

查看 CreativesLibrary/Components 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。