You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dfd37db
Browse filesBrowse the repository at this point in the historyBrowse files
Make rush add and upgrade-interactive catalog-aware
"rush add" writes PNPM catalog references (catalog: / catalog:<name>)
when a catalog of the project's subspace has a matching entry, accepts
explicit catalog references, and with --make-consistent updates the
catalog entry instead of replacing references with versions. A project's
existing catalog reference is never silently replaced with a version.
"rush upgrade-interactive" lists dependencies referenced through a
catalog and upgrades them by bumping the catalog entry. When the updated
pnpm-config.json is shared with other subspaces, the needed
"rush update --subspace" commands are printed.
npm-check-fork now honors a provided cwdPackageJson.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
"comment": "Make \"rush add\" and \"rush upgrade-interactive\" aware of PNPM catalogs. \"rush add\" now writes a catalog reference (such as \"catalog:\" or \"catalog:tools\") instead of a version when a catalog of the project's subspace has an entry for the package that matches the requested version (or when no version is specified), and accepts explicit catalog references such as \"rush add -p example@catalog:tools\". With \"--make-consistent\", the catalog entry in pnpm-config.json is updated instead of replacing catalog references with versions. A project's existing catalog reference is never replaced with a version. \"rush upgrade-interactive\" now lists dependencies that are referenced through a catalog, and upgrades them by updating the catalog entry. When the updated pnpm-config.json is shared with other subspaces, Rush prints the \"rush update --subspace\" commands that are needed to update their shrinkwrap files.",
"comment": "Use the \"cwdPackageJson\" option when it is provided, instead of always reading package.json from the \"cwd\" folder. The default options are no longer modified by each call.",
Copy file name to clipboardExpand all lines: libraries/rush-lib/src/api/test/__snapshots__/RushCommandLine.test.ts.snap
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Object {
15
15
"shortName": "-s",
16
16
},
17
17
Object {
18
-
"description": "The name of the package which should be added as a dependency. A SemVer version specifier can be appended after an \\"@\\" sign. WARNING: Symbol characters are usually interpreted by your shell, so it's recommended to use quotes. For example, write \\"rushadd--package \\"example@^1.2.3\\"\\" instead of \\"rushadd--packageexample@^1.2.3\\". To add multiple packages, write \\"rushadd--packagefoo--packagebar\\".",
18
+
"description": "The name of the package which should be added as a dependency. A SemVer version specifier or a PNPM catalog reference (such as \\"catalog:\\" or \\"catalog:tools\\") can be appended after an \\"@\\" sign. WARNING: Symbol characters are usually interpreted by your shell, so it's recommended to use quotes. For example, write \\"rushadd--package \\"example@^1.2.3\\"\\" instead of \\"rushadd--packageexample@^1.2.3\\". To add multiple packages, write \\"rushadd--packagefoo--packagebar\\".",
0 commit comments