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

@clinic/heap-profiler

v5.0.0

Published

Programmable interface to Clinic.js Heap Profiler

Downloads

97,160

Readme

Clinic.js Heap Profiler

npm version Stability Stable Github Actions build status Downloads Code style

Programmable interface to Clinic.js Heap Profiler. Learn more about Clinic.js: https://clinicjs.org/

screenshot

Issues

To open an issue, please use the main repository with the heapprofiler label.

Installation

npm i -S @clinic/heap-profiler

Supported node versions

  • Node.js 16 and above

Example

const ClinicHeapProfiler = require('@clinic/heap-profiler')
const heapProfiler = new ClinicHeapProfiler()

heapProfiler.collect(['node', './path-to-script.js'], function (err, filepath) {
  if (err) throw err

  heapProfiler.visualize(filepath, filepath + '.html', function (err) {
    if (err) throw err
  })
})

Documentation

const ClinicHeapProfiler = require('@clinic/heap-profiler')
const heapProfiler = new ClinicHeapProfiler()

new ClinicHeapProfiler([settings])

  • settings <Object>
    • detectPort <boolean> Default: false
    • collectOnFailure <boolean> If set to true, the collected data will be returned even if the process exits with non-zero code. Default: false
    • debug <boolean> If set to true, the generated html will not be minified. Default: false
    • dest <String> Destination for the collected data Default: .clinic
    • name <String> File name for the collected data Default: <process.pid>.clinic-heapprofiler

heapProfiler.collect(args, callback)

Starts a process by using @nearform/heap-profiler.

The process sampling is started as soon as the process starts. The filepath with collected data will be the value in the callback.

stdout, stderr, and stdin will be relayed to the calling process.

The sampling is stopped and data collected right before the process exits.

If you want to collect data earlier, you can send the process a SIGINT or, if detectPort is true, you can call heapProfiler.stopViaIPC().

heapProfiler.visualize(dataFilename, outputFilename, callback)

Will consume the datafile specified by dataFilename, this datafile will be produced by the sampler using heapProfiler.collect.

heapProfiler.visualize will then output a standalone HTML file to outputFilename. When completed the callback will be called with no extra arguments, except a possible error.

heapProfiler.stopViaIPC()

When the profiler is started with detectPort=true, the profiler establish a TCP based IPC communication.

This method can therefore be called to collect the data at any time.

If no TCP channel is opened or available, the method will perform no operation so it is safe to call at all times.

Examples

See the examples folder. All example should be run from the repository main folder:

node examples/redis-web-service

Each index.js will contain any specific setup step required by the example, if any.

License

MIT