Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

types gen: unresolved-source error for rotted remote bundle URLs is opaque — published configs carry ephemeral preview URLs that can 404

Abierto
  • ¿Algo no está bien?
#652 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend

Línea de trabajo

Start by reading the strict runtime-map change in #594 and the getAssociatedUi path; the issue does not name source files or tests. Trace how remote manifest fetch failures become unresolved-source errors, then check the existing ui: false and BOS_MAP_ALLOW_UNRESOLVED=1 behavior. Done means the error identifies the owning app and gateway, whether the slot was inherited, and the remediations.

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

Descripción

Found during the nearbuilders.org v2 upgrade (NEARBuilders/nearbuilders.org#305).

What

The strict runtime-map (#594) is right to fail on unresolved sources, but the failure gives no actionable context:

ERROR (#54): [runtime-map] UNRESOLVED nostr (plugin-ui): fetch https://elliot-braem-9129-ui-nostr-nearbuilders-org-nearb-b7951b19d-ze.zephyrcloud.app/manifest.gen.json failed: HTTP 404 Not Found

The URL came from a v1 published config (nostr.nearbuilders.org) whose app.ui points at an ephemeral Zephyr preview bundle that has since been deleted. The consumer inherits the slot via getAssociatedUi when extending #plugins.<id>, and CI (consumer-ci → pnpm run typecheck → bos types gen) fails with no hint that (a) the owning app is nostr.nearbuilders.org, (b) the URL is a rotted Zephyr preview from a v1-era publish, or (c) the fixes are: upgrade/publish the source app to v2, ui: false on the extending entry (shipped in rc.25 / #636), or BOS_MAP_ALLOW_UNRESOLVED=1.

Suggested fix

When a remote manifest fetch fails, the unresolved-source error should include: the owning app/account + gateway of the extends source, whether the slot was inherited via getAssociatedUi (vs declared locally), and the known remediations. It took a multi-repo investigation (nostr PR #32's known issues + activity #82's commit 8) to learn this failure mode; the error should teach it.

Backdrop

#282 removed Zephyr from the platform's own deploy path, but v1-era published configs still carry Zephyr preview URLs and they rot silently — consumers extending stale v1 remotes are the population that keeps hitting this. Longer term, publish canonicalization could refuse/deny ephemeral preview hosts so this class of published config can't be created.

Lenguaje dominante
TypeScript
Estrellas
5
Forks
3
Merge medio
9 h 37 min
PR fusionados (30 d)
157

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 NEARBuilders/everything-dev

Todos los issues de NEARBuilders/everything-dev

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.