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

[rush] Expected that the rush update-autoinstaller command can sync the rush-plugins manifest.json files to the rush-plugins directory

Abierto
#5,465 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
nodejs, typescript
Área
build-system, tooling

Línea de trabajo

Start with the implementation of rush update-autoinstaller --name rush-plugins and trace how it handles autoinstallers/rush-plugins/package.json and manifest files. Reproduce the command, then verify that each rush-plugin-manifest.json is copied into the rush-plugins directory and that the subsequent pnpm-lock.yaml update detects missing package files.

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

Descripción

Summary

Currently, after running rush update-autoinstallers, the rush-plugin-manifest.json file is not copied to rush-plugins directory. Instead, it requires running rush update to trigger the sync of this file. This is somewhat counterintuitive in terms of usage.

Meanwhile, during development, it can also easily lead to the omission of the rush-plugin-manifest.json file. The development process is as follows:

  1. Develop the plugin locally and declare it in autoinstallers/rush-plugins/package.json using link:./<path_to>/my-rush-plugin.
  2. After testing is completed, the my-rush-plugin/rush-plugin-manifest.json file has already been saved in the git repository.
  3. Assuming that the rush-plugin-manifest.json file is not declared in the files field of my-rush-plugin's package.json, it is difficult for CI to detect this issue at this point. This is because CI usually runs the install command, and only rush update can identify this problem.

If rush update-autoinstaller tried to copy the manifest files, than in the update pnpm-lock.yaml step, the problem will be detected.

Repro steps

Run rush update-autoinstaller --name rush-plugins

Expected result: The rush-plugin-manifest.json files will be copied to the rush-plugins directory.

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question Answer
@microsoft/rush globally installed version? 5.155.1
rushVersion from rush.json? 5.155.1
useWorkspaces from rush.json? Yes
Operating system? Mac
Would you consider contributing a PR? Yes
Node.js version (node -v)? 22.20.0
Lenguaje dominante
TypeScript
Estrellas
6.5k
Forks
708
Merge medio
4 d 13 h
PR fusionados (30 d)
62

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 microsoft/rushstack

Todos los issues de microsoft/rushstack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.