[rush] Expected that the rush update-autoinstaller command can sync the rush-plugins manifest.json files to the rush-plugins directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- nodejs, typescript
- Domain
- build-system, tooling
Research direction
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.
Written by the indexing model from the issue text.
Description
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:
- Develop the plugin locally and declare it in autoinstallers/rush-plugins/package.json using
link:./<path_to>/my-rush-plugin. - After testing is completed, the my-rush-plugin/rush-plugin-manifest.json file has already been saved in the git repository.
- 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 |
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 62
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoft/rushstack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 88/100