7.0.1 (2022-10-19)
7.0.0 (2022-10-14)
npmlogis now compatible with the following semver range for node:^14.17.0 || ^16.13.0 || >=18.0.0
6.0.2 (2022-04-20)
- update gauge requirement from ^4.0.0 to ^4.0.1 (cf52b06)
- update gauge requirement from ^4.0.1 to ^4.0.2 (#96) (53063a9)
- update gauge requirement from ^4.0.2 to ^4.0.3 (#101) (929686c)
- Drop support for node 10 and non-lts versions of 12 and 14
6.0.1 (2022-02-09)
- @npmcli/[email protected] (5e7b9f4)
- [email protected] (7aefa36)
- update are-we-there-yet to v2.0.0.
- Drop support for node versions 6 and 8
- Fix bug where gauge was enabled when paused
- Added installation instructions.
- Fix bugs where
log.progressEnabledgot out of sync with howgaugekept track of these things resulting in a progressbar that couldn't be disabled.
- Allow creating log levels that are an empty string or 0.
- Update to
[email protected]adding support for default values for template items.
- Update to
[email protected]to fix to1.xcompatibility when it comes to when a progress bar is enabled. In1.xif you didn't have a TTY the progress bar was never shown. In2.xit merely defaults to disabled, but you can enable it explicitly if you still want progress updates.
- Update to
[email protected]:- Updates the
signal-exitdependency which fixes an incompatibility with the node profiler. - Uses externalizes its ansi code generation in
console-control-strings
- Updates the
- Make the default progress bar include the last line printed, colored as it would be when printing to a tty.
- Switch to
[email protected], for better performance, better look. - Set stderr/stdout blocking if they're tty's, so that we can hide a progress bar going to stderr and then safely print to stdout. Without this the two can end up overlapping producing confusing and sometimes corrupted output.
- Make the
errorevent non-fatal so that folks can use it as a prefix.
- Add progress bar with
[email protected]