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 摘要。