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

logtrap

v0.0.1

Published

Clean up lingering brew dependencies

Downloads

22

Readme

logtrap

Capture stdout/stderr for testing purposes

Why?

To test applications where the output matters

Usage

Install logtrap

  $ npm install logtrap

Setup tests that need to capture output

  require 'mocha'
  { expect } = require 'chai' # or your favorite assertion tool
  { stdoutTrap, stderrTrap } = require 'logtrap'

# Some function that outputs to stdout
  logger = (type, msg) -> console[type] "#{type}: #{msg}"

# Test
  describe 'Capture outputs', ->
    it 'should suppress stderr and capture instead', ->
      good = stdoutTrap -> logger 'log', "All systems go!"
      expect(good).to.equal "log: All systems go!\n"
    it 'should suppress stderr and capture instead', ->
      bad = stderrTrap -> logger 'error', "It's a trap"
      expect(bad).to.equal "error: It's a trap\n"

View pretty test results

  # Test outputs
  Capture console.log
    ✓ should suppress stderr and capture instead
    ✓ should suppress stderr and capture instead

  # Note that the test results are not polluted with the output logs

Notes

  • [^.^]

License

Logtrap is released under the MIT License.