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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@codefresh-io/cf-telemetry

v3.8.1

Published

Base utils for monitoring.

Readme

cf-telemetry

Base utils for monitoring.

Includes:

Usage

Add import '@codefresh-io/cf-telemetry/init' statement at the very beginning of the application lifecycle.

Please refer to the separate docs above for further configuration and usage details.

// index.ts
// ↓ Should be imported first
import '@codefresh-io/cf-telemetry/init'
// ↓ Keep one blank line below to prevent automatic import reordering

Lifecycle notices

[!IMPORTANT] Please read this section carefully to understand how this library handles application lifecycle events and how it affects application lifecycle.

This library registers listeners for SIGINT, SIGTERM and beforeExit events to gracefully terminate instrumentation, which may include flushing logs, metrics, and profiles.

Effect on application lifecycle

As this library registers listeners for SIGINT and SIGTERM events, Node.js' default handlers for such signals will be removed: Node.js will no longer exit on non-Windows platforms on such signals. More details in the doc.

Please make sure you add your own exit handlers for these signals.

Instrumentation shutdown

None of the events above happens if proces.exit() is called directly. This means that if you call process.exit() in your application, the library will not be able to gracefully terminate instrumentation. This may lead to loss of logs, metrics, and other telemetry data.

Please ensure calling terminate() method of this library before calling process.exit() to ensure graceful termination of instrumentation.

import { terminate } from '@codefresh-io/cf-telemetry/init'

// ...your application logic
await terminate();    // Ensure graceful termination of instrumentation
process.exit(0);      // Now it's safe to exit the process

Environment variables

| Variable | Required | Default value | Description | |------------------------| -------- |-------------------------------------------------------------------|---------------------------------------------| | CF_SERVICE_NAME | optional | unknown_service:node | Sets service name for OpenTelemetry, Pyroscope and Prometheus. | | CF_SERVICE_VERSION | optional | unknown | Sets service name for OpenTelemetry, Pyroscope and Prometheus. |