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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sentry/profiling-node

v11.8.0

Published

Official Sentry SDK for Node.js Profiling

Downloads

12,264,349

Readme

Official Sentry Profiling SDK for NodeJS

npm version npm dm npm dt

Profiling for Node.js applications.

Documentation

Building the package from source

Profiling uses native modules to interop with the v8 javascript engine which means that you may be required to build it from source. The libraries required to successfully build the package from source are often the same libraries that are already required to build any other package which uses native modules and if your codebase uses any of those modules, there is a fairly good chance this will work out of the box. The required packages are python, make and g++.

Windows: If you are building on windows, you may need to install Visual Studio's C++ build tools.

macOS: Install Xcode Command Line Tools for the compiler and make.

See the node-gyp prerequisites for supported Python versions and platform-specific requirements.

After you have installed the toolchain, you should be able to build the binaries from source. The native bindings are maintained in the Node CPU profiler repository. Clone that repository, install its dependencies with yarn install --ignore-scripts, and run the following from its root:

# configure node-gyp using yarn
yarn build:bindings:configure
# or using npm
npm run build:bindings:configure

# compile the binaries using yarn
yarn build:bindings
# or using npm
npm run build:bindings

After the binaries are built, you should see them inside that repository's lib folder.

Prebuilt binaries

We currently ship prebuilt binaries for a few of the most common platforms and node versions.

  • macOS x64
  • Linux ARM64 (musl)
  • Linux x64 (glibc)
  • Windows x64

For a more detailed list, see the job_compile job in the native build workflow.

Support