Merge pull request #25 from octogonz/main

Upgrade to Rush 5.153.2

Author: octogonz

common/config/rush/.npmrc

@@ -22,5 +22,12 @@
 #
 #   //registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}
 #
+
+# Explicitly specify the NPM registry that "rush install" and "rush update" will use by default:
 registry=https://registry.npmjs.org/
+
+# Optionally provide an authentication token for the above registry URL (if it is a private registry):
+# //registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}
+
+# Change this to "true" if your registry requires authentication for read-only operations:
 always-auth=false

common/config/rush/.npmrc-publish

@@ -18,3 +18,9 @@
 #
 #   //registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}
 #
+
+# Explicitly specify the NPM registry that "rush publish" will use by default:
+registry=https://registry.npmjs.org/
+
+# Provide an authentication token for the above registry URL:
+# //registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}

common/config/rush/experiments.json

@@ -102,5 +102,20 @@
   /**
    * When using cobuilds, this experiment allows uncacheable operations to benefit from cobuild orchestration without using the build cache.
    */
-   // "allowCobuildWithoutCache": true
+   // "allowCobuildWithoutCache": true,
+
+   /**
+   * By default, rush perform a full scan of the entire repository. For example, Rush runs `git status` to check for local file changes.
+   * When this toggle is enabled, Rush will only scan specific paths, significantly speeding up Git operations.
+   */
+  // "enableSubpathScan": true,
+
+  /**
+   * Rush has a policy that normally requires Rush projects to specify `workspace:*` in package.json when depending
+   * on other projects in the workspace, unless they are explicitly declared as `decoupledLocalDependencies`
+   * in rush.json.  Enabling this experiment will remove that requirement for dependencies belonging to a different
+   * subspace.  This is useful for large product groups who work in separate subspaces and generally prefer to consume
+   * each other's packages via the NPM registry.
+   */
+  // "exemptDecoupledDependenciesBetweenSubspaces": false
 }

common/config/rush/pnpm-config.json

@@ -1,6 +1,11 @@
 /**
  * This configuration file provides settings specific to the PNPM package manager.
  * More documentation is available on the Rush website: https://rushjs.io
+ *
+ * Rush normally looks for this file in `common/config/rush/pnpm-config.json`.  However,
+ * if `subspacesEnabled` is true in subspaces.json, then Rush will instead first look
+ * for `common/config/subspaces/<name>/pnpm-config.json`.  (If the file exists in both places,
+ * then the file under `common/config/rush` is ignored.)
  */
 {
   "$schema": "https://developer.microsoft.com/json-schemas/rush/v5/pnpm-config.schema.json",
@@ -167,7 +172,7 @@
     //    * Enables the "disallowInsecureSha1" policy.  The default value is false.
     //    */
     //   "enabled": true,
-    // 
+    //
     //   /**
     //    * In rare cases, a private NPM registry may continue to serve SHA1 hashes for very old
     //    * package versions, perhaps due to a caching issue or database migration glitch.  To avoid
@@ -272,9 +277,9 @@
    *
    * PNPM documentation: https://pnpm.io/package_json#pnpmignoredoptionaldependencies
    */
-  "globalIgnoredOptionalDependencies": [
+  //"globalIgnoredOptionalDependencies": [
     // "fsevents"
-  ],
+  //],
 
   /**
    * The `globalAllowedDeprecatedVersions` setting suppresses installation warnings for package

common/scripts/install-run-rush.js

@@ -16,7 +16,7 @@
    * path segment in the "$schema" field for all your Rush config files.  This will ensure
    * correct error-underlining and tab-completion for editors such as VS Code.
    */
-  "rushVersion": "5.141.2",
+  "rushVersion": "5.153.2",
 
   /**
    * The next field selects which package manager should be installed and determines its version.