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

tracer-component

v0.1.0-20230213204243.commit-a69f42d

Published

Trace execution spans all across your application.

Downloads

8

Readme

Tracer component

This component creates trace spans over an execution, providing context to the code being executed so it can be traced.

Usage

The tracer component is pretty straightforward to use, just import the component, initialize it and wrap your traceable code into a trace span:

import { createTracerComponent } from '@well-known-components/tracer-component'

const tracer = createTracerComponent()
tracer.span('my span', () => {
  // Do some work here
})

While being into the span, the traced code is able to access the trace context, this is specially useful if we want to add traced logs to our code:

const tracer = createTracerComponent()
tracer.span('my span', () => {
  console.log(`[${tracer.getTraceString()}] Starting some work`)
  // Do some work here
  console.log(`[${tracer.getTraceString()}] Finishing some work`)
})

In the example given above, the logs will output a trace alongside the log message using the traceparent format.

  [00-7970d1a8361cc811ee59dc3ee1c8134e-0000000000000000-00] Starting some work
  [00-7970d1a8361cc811ee59dc3ee1c8134e-0000000000000000-00] Finishing some work

As seen in the example, the format is built as: version-traceId-parentId-flags. The trace id makes it easy to track which execution of the span we're logging and will be unique through the span execution. The parent id identifies the span id where the current span was created from, making it possible to track which span originated the current span. All of this values, including version and flags values can be seen in the traceparent format document.