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

async-log

v0.1.0

Published

Utility and sample code for logging async operations in the context of a web-server using the async_hooks core api

Downloads

1

Readme

async-log

Utility and sample code for logging async operations in the context of a web-server using the async_hooks core api

Requirements

  • node: > 8.1.0

Use the helper

(you can view the demo.js file for all the details)

  • add it as a dependency

    yarn add async-log,

  • include it in your main entry point

    const asyncLog = require('async-log');

  • create a transaction every time your server handles a request

    const trans = asyncLog.newTransaction({
     url: req.url,
    });
  • end the transaction every time your server finished handling the request

    trans.end();
  • in between these two calls, every time you want to track fetching a remote resource you need to create a new trace before, then end the created trace after

    const trace = asyncLog.newTrace({ type: 'db' });
    //...
    trace.end();

Use the demo

  • clone this repo and change directory to it's folder

  • start the server in one tab

    node demo.js
  • make request to the server in another tab

    curl http://localhost:3131/ & curl http://localhost:3131/yoyo & wait
  • in the initial tab, you will see how much each request took, and out of that how much it waited for async resources (file access, network requests, etc.)

Caveats

  • the async wait measurements also include some overhead. So it's not 100% accurate. I consider it close enough for my needs.

Acknowledgements

This is inspired by this talk from Thomas Watson and his example code