npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

keep-silent

v1.2.0

Published

keep console silent

Downloads

7

Readme

keep-silent Build Status js-standard-style

Keep console silent.

The output console.log may disturb normal testing log when you test some code which contains console output, keep-silent will help you to solve it.

Example usage:

const silent = require('keep-silent')
const assert = require('assert')

function output() {
  console.log('output some console logs for user')
  console.log('CATCH ME!')
}

silent(function (log) {
  output()

  assert(log.contains('CATCH ME'))
})

The silent function will capture console logs of it's callback, you can access caputred logs by param log.

Synopsis

Promise<String>|String silent(callback, options)

Arguments

callback

The callback can be a normal function or a generator function, you can return a Promise when your callback is async. Callback contains one parameter log, which has methods (see next section) for processing logs.

For async useage, we suggest use generator in slient callback just like co does:

slient(function * (log) {
  yield async1()
  assert(log.flush() === 'foo')

  yield async2()
  assert(log.flush() === 'bar')
})

options

  • errorOutput: print output when error occurs (default: true)

Return

If callback is sync, the return value will be full captured logs String. If callback is async (return Promise or Generator function), the return value will be a Promise with full captured logs String.

The captured logs will NOT lose even if you have called log.clear() or log.flush().

Parameter log

The methods and props of callback parameter log:

log.clear()

Clear captured logs, the log.value will be a empty String.

log.contains(part[, strip])

  • part, the part of log to check
  • strip, strip cli ansi color chars (default: false)

Whether logs contain specified string, the part can be a String or RegExp object.

log.flush()

Clear captured logs and return it, the log.value will be a empty String.

log.value

Current captured logs.

Example

Keep some function slient:

const silent = require('keep-silent')

// keep silent (sync case)
let captured = silent(function () {
  outputSync('bla bla bla ....')
})

// keep silent (promise)
silent(function () {
  return outputPromise('do some async work ...')
}).then(function (captured) {
  // do what you like
})

// keep silent (generator)
silent(function * () {
  yield outputAsync('do some async work ...')
}).then(function (captured) {
  // do what you like
})

Capture logs for unit test (with mocha):

const assert = require('assert')
const silent = require('keep-silent')

function outputSync() {
  console.log('hello')
}

function outputAsync() {
  return new Promise(resolve => {
    setTimeout(_ => {
      console.log('world')
      resolve()
    }, 100)
  })
}

function dump() {
  console.log('just dump annoyed text .... HAHAHA LALALA')
}

describe('Testing for demo', function () {
  it('should output hello', function () {
    silent(function (log) {
      outputSync()
      assert(log.flush() === 'hello\n')

      dump()
      assert(log.contains('HAHAHA'))
    })
  })

  it('should output world', function () {
    return silent(function * (log) {
      yield outputAsync()
      assert(log.value === 'world\n')
    })
  })
})

License

MIT