gauge
Advanced tools
Changelog
v2.7.3
- Only create our onExit handler when we're enabled and remove it when we're disabled. This stops us from creating multiple onExit handlers when multiple gauge objects are being used.
- Fix bug where if a theme name were given instead of a theme object, it would crash.
- Remove supports-color because it's not actually used. Uhm. Yes, I just updated it. >.>
Changelog
v2.7.1
- Bug fix: Calls to show/pulse while the progress bar is disabled should still update our internal representation of what would be shown should it be enabled.
Changelog
v2.7.0
- New feature: Add new
isEnabledmethod to allow introspection of the gauge's "enabledness" as controlled by.enable()and.disable().
Changelog
v2.6.0
- Bug fix: Don't run the code associated with
enable/disableif the gauge is already enabled or disabled respectively. This prevents leaking event listeners, amongst other weirdness. - New feature: Template items can have default values that will be used if no value was otherwise passed in.
Changelog
v2.5.3
- Default to
enabledonly if we have a tty. Users can always override this by passing in theenabledoption explicitly or by calling callinggauge.enable().
Changelog
v2.5.1
- Update to
signal-exit@3.0.0, which fixes a compatibility bug with the node profiler. - #39 Fix tests on 0.10 and add a missing devDependency. (@helloyou2012)