nf publish gives no warning for invalid contents entries or a package with no contents

Abierto
  • ¿Algo no está bien?
#262 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli

Línea de trabajo

Start at the publish command and trace how it calls readPackageContents from @nanoforge-dev/registry; the issue says that function returns problems and that invalid entries are omitted from the archive. Check how the command handles flags and reports the file list. Done means it warns about those problems and an otherwise empty package, and refuses to publish in both cases unless the chosen force flag is set.

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

Descripción

command:publish enhancement
Which package is this feature request for?

@nanoforge-dev/cli

Which command is this feature request for?

publish

Feature

nf publish gives no warning when the manifest's contents has entries @nanoforge-dev/registry can't read (an invalid kind, or a path like ./src/). Those paths are left out of the archive without a word, and the registry may refuse the manifest only after the upload. A manifest with no contents publishes only the manifest and the README/LICENSE/CHANGELOG files, with no warning either.

Ideal solution or implementation

Print the problems that readPackageContents returns as warnings before the file list, and warn when nothing but the root files would be packed. Refuse in both cases unless a flag such as --force is given.

Alternative solutions or implementations

Warnings only, never refusing.

Other context

Found during the feat/registry-lib change (not merged yet): @nanoforge-dev/registry moves from the editor to libs/registry, and nf install/publish/unpublish use it.

Lenguaje dominante
TypeScript
Estrellas
2
Forks
2
Merge medio
2 d 18 h
PR fusionados (30 d)
17

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 NanoForge-dev/CLI

Todos los issues de NanoForge-dev/CLI

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.