log-update

v6.1.0

Log by overwriting the previous output in the terminal. Useful for rendering progress bars, animations, etc. For more information about how to use this package see README

Latest version published 3 months ago

License: MIT

NPM

GitHub

Package Health Score

80 / 100

security
No known security issues
popularity
Influential project
maintenance
Sustainable
community
Sustainable

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
6.1.0	\|	07/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.0.0	\|	10/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.0.1	\|	04/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.0.0	\|	02/2020	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.4.0	\|	02/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (18,200,539)

GitHub Stars: 1.09K
Forks: 40
Contributors: 20

Direct Usage Popularity

The npm package log-update receives a total of 18,200,539 downloads a week. As such, we scored log-update popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package log-update, we found that it has been starred 1,094 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: Yes
Contributors: 20
Funding: Yes

With more than 10 contributors for the log-update repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 5
Open PR: 0
Last Release: 3 months ago
Last Commit: 3 months ago

Further analysis of the maintenance status of log-update based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that log-update demonstrates a positive version release cadence with at least one new version released in the past 3 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=18

Age: 9 years
Dependencies: 5 Direct
Versions: 19
Install Size: 7.58 kB
Dist-tags: 1
# of Files: 5
Maintainers: 1
TS Typings: No

log-update has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use log-update?

To help you get started, we've collected the most common ways that log-update is being used within popular public projects.

yvele / poosh / packages / poosh-cli / src / Logger.js View on Github

function display() {

  if (this._logBuffer.length) {
    logUpdate.clear();

    // eslint-disable-next-line no-console
    console.log(this._logBuffer.join("\n"));

    this._logBuffer = [];
  }

  logUpdate(this._warningLine
    + output.getMatchingLine(this._status)
    + output.getUploadingLine(this._status)
    + output.getDeletingLine(this._status)
    + output.getStatLine(this._status)
    + output.getElapsedLine(this._status));
}

View more ways to use log-update

log-update

Log by overwriting the previous output in the terminal.
Useful for rendering progress bars, animations, etc.

Install

npm install log-update

Usage

import logUpdate from 'log-update';

const frames = ['-', '\\', '|', '/'];
let index = 0;

setInterval(() => {
	const frame = frames[index = ++index % frames.length];

	logUpdate(
`
        ♥♥
   ${frame} unicorns ${frame}
        ♥♥
`
	);
}, 80);

API

logUpdate(text…)

Log to stdout.

logUpdate.clear()

Clear the logged output.

logUpdate.done()

Persist the logged output.

Useful if you want to start a new log session below the current one.

logUpdateStderr(text…)

Log to stderr.

logUpdateStderr.clear()

logUpdateStderr.done()

createLogUpdate(stream, options?)

Get a logUpdate method that logs to the specified stream.

options

Type: object

showCursor

Type: boolean
Default: false

Show the cursor. This can be useful when a CLI accepts input from a user.

import {createLogUpdate} from 'log-update';

// Write output but don't hide the cursor
const log = createLogUpdate(process.stdout, {
	showCursor: true
});

Examples

listr - Uses this module to render an interactive task list
ora - Uses this module to render awesome spinners
speed-test - Uses this module to render a spinner

log-update dependencies

ansi-escapes cli-cursor slice-ansi strip-ansi wrap-ansi

log-update development dependencies

@types/node ava terminal.js tsd wcwidth xo

FAQs

What is log-update?

Log by overwriting the previous output in the terminal. Useful for rendering progress bars, animations, etc. Visit Snyk Advisor to see a full health score report for log-update, including popularity, security, maintenance & community analysis.

Is log-update popular?

The npm package log-update receives a total of 18,200,539 weekly downloads. As such, log-update popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is log-update well maintained?

We found indications that log-update maintenance is sustainable demonstrating some project activity. We saw a total of 20 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is log-update safe to use?

The npm package log-update was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 5 November-2024, at 05:15 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (18,200,539)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use log-update?

log-update

Install

Usage

API

logUpdate(text…)

logUpdate.clear()

logUpdate.done()

logUpdateStderr(text…)

logUpdateStderr.clear()

logUpdateStderr.done()

createLogUpdate(stream, options?)

options

showCursor

Examples

log-update dependencies

log-update development dependencies

FAQs

What is log-update?

Is log-update popular?

Is log-update well maintained?

Is log-update safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues