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

Abierto
#91 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, node.js, react, tailwindcss
Área
frontend, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
JavaScript
Estrellas
17
Forks
7
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CreativesLibrary/Components

Todos los issues de CreativesLibrary/Components

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.