@rushstack/stream-collator 4.0.197 → 4.0.200

package/dist/tsdoc-metadata.json

@@ -5,7 +5,7 @@
   "toolPackages": [
     {
       "packageName": "@microsoft/api-extractor",
-      "packageVersion": "7.29.3"
+      "packageVersion": "7.29.5"
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rushstack/stream-collator",
-  "version": "4.0.197",
+  "version": "4.0.200",
   "description": "Display intelligible realtime output from concurrent processes",
   "repository": {
     "type": "git",
@@ -11,13 +11,13 @@
   "typings": "dist/stream-collator.d.ts",
   "license": "MIT",
   "dependencies": {
-    "@rushstack/node-core-library": "3.51.0",
-    "@rushstack/terminal": "0.3.66"
+    "@rushstack/node-core-library": "3.51.1",
+    "@rushstack/terminal": "0.3.69"
   },
   "devDependencies": {
     "@rushstack/eslint-config": "3.0.0",
-    "@rushstack/heft": "0.47.4",
-    "@rushstack/heft-node-rig": "1.10.4",
+    "@rushstack/heft": "0.47.5",
+    "@rushstack/heft-node-rig": "1.10.7",
     "@types/heft-jest": "1.0.1",
     "@types/node": "12.20.24"
   },
@@ -25,6 +25,5 @@
     "build": "heft build --clean",
     "_phase:build": "heft build --clean",
     "_phase:test": "heft test --no-build"
-  },
-  "readme": "## @rushstack/stream-collator\n\nThis library enables a tool to display live console output from multiple concurrent processes,\nwhile ensuring that their output does not get jumbled together.\n\n## How does it work?\n\nThe **stream-collator** manages the output of these streams, ensuring that no two streams are writing to the console\nat the same time. At any given time, one stream registered with the collator is the **active stream**, which means\nthat particular stream will be live streaming, while the others will wait for that stream to finish before their\noutput is displayed.\n\nFor example, if you have 3 streams (e.g. from using `child_process.spawn()`).\n\nStream A will write: `AAAAA`\n\nStream B will write: `BBBBBBBBBBBBBBBBBBBB`\n\nStream C will write: `CCCCCCCCCC`\n\nIf these streams are all being piped directly to stdout (without `@rushstack/stream-collator`), you could end up\nwith jumbled output:\n\n`ABACCCBCCCCBBABBCBBABBBBBBCCAB`\n\nSomething like the following would be much more useful to users of your application:\n\n`AAAAABBBBBBBBBBBBBBBCCCCCCCCCC`\n\nThis is where the `@rushstack/stream-collator` comes in!\n\n## The active stream\n\nAt any given time, a single stream is designated as the **active stream**. The output of the active stream will always be\nlive-streamed. This is particularly useful for long-running streams. When the active stream finishes, a new stream\nis selected as the active stream and all of its contents up to that point will be emitted. Whenever an active stream finishes,\nall background streams which have been completed will be emitted.\n\n## Usage\n\n> 🚨 _This is an early preview release. Please report issues!_ 🚨\n>\n> WITH VERSION 4.X, THIS PACKAGE HAS BEEN REDESIGNED TO USE THE NEW\n> [@rushstack/terminal](https://www.npmjs.com/package/@rushstack/terminal) SYSTEM.\n> IN THE NEXT RELEASE, THE `CollatedTerminal` API WILL BE REPLACED WITH\n> THE `Terminal` API.\n>\n> The usage instructions will be updated once that refactoring is complete.\n\n## Links\n\n- [CHANGELOG.md](\n  https://github.com/microsoft/rushstack/blob/main/libraries/stream-collator/CHANGELOG.md) - Find\n  out what's new in the latest version\n- [API Reference](https://rushstack.io/pages/api/stream-collator/)\n\n`@rushstack/stream-collator` is part of the [Rush Stack](https://rushstack.io/) family of projects.\n"
+  }
 }