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

debug.trace

v1.0.1

Published

Debugging tool that compliments FP-style code

Downloads

10

Readme

debug.trace

A small trace utility that allows debugging info to be printed from any function pipeline.

Why not just console.log?

I'm lazy. It takes a few seconds to convert some arrow functions into a form that allows console.log.

For example,

const add = (x, y) => x + y

// What was x and y?
// I have to modify the add function with curly braces and a return.
const add = (x, y) => {
  console.log('x', x)
  console.log('y', y)
  return x + y
}

// Or with trace I can leave everything inline, and still have the same effect.
const add = (x, y) => trace('x')(x) + trace('y')(y)

// Can even trace the result before returning.
const add = (x, y) => trace('result')(trace('x')(x) + trace('y')(y))

If you use compose from Ramda or Lodash, then you can simply sprinkle traces throughout the pipeline.

const R = require('ramda')
const trace = require('debug.trace')

const f = R.compose(trace('result'), R.multiply(2), trace('before multiply'), R.subtract(R.__, 1))
f(10) // prints "before multiply 9", "result 18", then returns 18

Usage

const trace = require('trace')

const x = 1
trace('what is x?')(1) // prints 'what is x? 1'

You can also import to globals automatically.

require('trace/global')

trace(...)

API

trace :: String -> A -> A

Prints a message and value, then return the original value. Arguments are curried.

const trace = require('debug.trace')
trace('Hello', 'World') // => 'Hello World' is printed
trace('Hello')('World') // => 'Hello World' is printed
trace('x', 'y') === 'y' // true

traceP :: String -> Promise A -> Promise A

Prints a message and resolved promise value, then return the promise. Arguments are curried.

const traceP = require('debug.trace').traceP
traceP('Hello', Promise.resolve('World')) // => 'Hello World' is printed
traceP('Hello')(Promise.resolve('World')) // => 'Hello World' is printed
traceP('x', Promise.resolve('y')).then((a) => a === 'y') //resolves to true

traceStack :: String -> A -> A

Prints a message and value, then prints the stack trace, and returns original value. Arguments are curried.

const traceStack = require('debug.trace').traceStack
traceStack('Hello', 'World') // => 'Hello World' is printed
// stack trace is printed
traceStack('Hello')('World') // => 'Hello World' is printed
// stack trace is printed
traceStack('x', 'y') === 'y' // true
// stack trace is printed