multi-progress-bars - npm Package Compare versions

Comparing version 2.0.1 to 2.0.2

CHANGELOG.md

@@ -5,2 +5,9 @@ # Changelog
 
+### [2.0.2](https://github.com/kamiyo/multi-progress-bars/compare/v2.0.1...v2.0.2) (2020-08-30)
+
+
+### Bug Fixes
+
+* **readme:** Updated readme. ([1813d01](https://github.com/kamiyo/multi-progress-bars/commit/1813d0149dd4ca142c3672baa193f5b3626a2602))
+
 ### [2.0.1](https://github.com/kamiyo/multi-progress-bars/compare/v2.0.0...v2.0.1) (2020-08-30)
@@ -7,0 +14,0 @@

package.json

 {
   "name": "multi-progress-bars",
-  "version": "2.0.1",
+  "version": "2.0.2",
   "description": "Multiple progress bars with option for indefinite spinners",
@@ -5,0 +5,0 @@ "main": "dist/multi-progress-bars.cjs.js",

README.md

 # multi-progress-bars
 ![npm shield](https://img.shields.io/npm/v/multi-progress-bars)
 
-A node library for displaying multiple progress bars, with an option for displaying indefinite tasks by using a spinner. Works well with gulp.js and/or webpack. This library will clear the screen (non-destructively by inserting newlines until the previous commands are above the fold), and display the bars from the top.
+A node library for displaying multiple progress bars, with an option for displaying indefinite tasks by using a spinner. Works well with gulp.js and/or webpack. This library will clear the screen (non-destructively by inserting newlines until the previous commands are above the fold), and display the bars from the top. Any subsequent calls to `console.log` will not affect the fixed progress rows; however, overflow will push previous console messages above the fold. This is enabled by a simple virtual console. This way no console messages will be lost. See the below demo .gif.
 
@@ -260,8 +260,8 @@ ![MultiProgressBar demo](./assets/mpb.gif)
 ## TODO
-* Make the cursor moving operations atomic with the other writes so we don't get thrashing if other stuff is being printed.
-    * Will require using ansi escape codes with one call to stdout.write instead of relying on Node's readline/stdout cursorTo and moveCursors; either that or use promises as a mutex for performing the move and the writes together.
-* Allow bars to be at top or at bottom, while allowing other logs to be printed
-    * Will require intercepting/overwriting default console.log or stdout.write. Not sure which would be better yet.
+* ~~Make the cursor moving operations atomic with the other writes so we don't get thrashing if other stuff is being printed.~~ Done!
+    * ~~Will require using ansi escape codes with one call to stdout.write instead of relying on Node's readline/stdout cursorTo and moveCursors; either that or use promises as a mutex for performing the move and the writes together.~~ Done!
+* ~~Allow bars to be at top~~ or at bottom, ~~while allowing other logs to be printed~~ Done for top! Lines preserved.
+    * ~~Will require intercepting/overwriting default console.log or stdout.write. Not sure which would be better yet.~~ See `virtual-console.ts`
 * Decouple hilbertSpinner from the instance.
 * Allow custom bar format
 * Allow custom progress format

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

56797

increased by1.07%

No dependency changes