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

trace-and-clarify-if-possible

v1.0.5

Published

Use `trace` and `clarify` if supported by the current node version

Downloads

9,136

Readme

trace-and-clarify-if-possible

NPM version Travis Build Status Coverage Status

Use trace and clarify if supported by the current node version

trace and clarify can help greatly to analyze stack-traces

  • trace shows the part of the stack that would otherwise disappear due to asynchronous callbacks
  • clarify removes uninteresting parts of the stack

Sadly, trace can is only compatible with NodeJS version >=4. It makes sense to include trace in your tests all the time (not in production code though). However, when you run the test in Travis CI with multiple node versions <4, the tests will break.

This package include trace and clarify only for supported node versions.

Installation

npm install trace-and-clarify-if-possible

Usage

Put the following line a module that is loaded at the start of your program or testcase-spec (remember, do not use in production).

require('trace-and-clarify-if-possible')

Or, you can put --require trace-and-clarify-if-possible into your test/mocha.opts` to activate it for all tests

License

trace-and-clarify-if-possible is published under the MIT-license.

See LICENSE.md for details.

Release-Notes

For release notes, see CHANGELOG.md

Contributing guidelines

See CONTRIBUTING.md.