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

console-goodies

v0.0.2

Published

console goodies

Downloads

9

Readme

console-goodies

Console goodies for debugging. :bug: :hammer:

Installation

yarn add console-goodies.

Usage

import 'console-goodies';

/* or */

require('console-goodies');

/**
 * console.group|time|profile call automatically their console.whateverEnd
 * counterpart when the function finishes.
 *
 */
console.group('group therapy', () => {
  console.log('foo');
  console.log('bar');
  console.log('lol');
});
/**
 * LOG:
 *
 *   group-therapy/
 *   ├── bar
 *   ├── foo
 *   └── lol
 */

console.time(() => {
  verySlowSyncFunction();
});
// LOG: 42000.1337ms ellapsed

/**
 * You can specify a label too
 */
console.time('this is soooo slow', () => {
  verySlowFunction();
});
// LOG: "this is so slow" 42000.1337ms ellapsed

/**
 * And they also work with async stuff! Promises or promise-returning functions
 * call their console.whateverEnd counterpart when the promise is fulfiled.
 */
console.time(() => {
  return new Promise((resolve) => setTimeout(resolve, 1000))
});
// LOG: 999.00000000002ms ellapsed

console.time('passing a promise directly', verySlowAsyncFunction());
// LOG: "passing a promise direcly" 300.00ms ellapsed

/**
 * console.tap
 *
 *   logs and returns a value: handy for peeking into stuff
 *   without having to create an intermediate variable just
 *   for debugging purposes.
 */
const f = () => 'f'
const u = () => 'u'
const c = () => 'c'
const k = () => 'k'
const fuck = () => f(u(console.tap(c(k))))
fuck();
// LOG: 'c'

/**
 * console.wtf
 *
 *   Because this is what we all do, most of the time.
 */
console.wtf();
// LOG: 'wtf'