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

ts-mem-trace

v0.0.3

Published

Memory Tracing for node and Typescript

Readme

ts-mem-trace

git repo: https://github.com/Lu9us/ts-mem-trace

ts-mem-trace is a node module designed to provide tracing and export of nodes memory use during the execution of a program.

To implement this ts-mem-trace wraps the data provided by process.memoryUsage().

to get the best results programs should be run with --expose_gc this allows for more control over when garbage collection happens.

paramaters:

init() can be passed a TraceMemoryUnit this controls the SI unit that the tracer exports its data in

  • allowed values:
    • Byte,
    • KiloByte,
    • MegaByte,
    • GigaByte,

output data:

  recordName: string; // the name provided when creating the trace
  memoryUnit: TraceMemoryUnit; //SI unit for the exported data
  heapTotal: number; // The total heap allocated to the node process
  heapUsed: number; // The total heap used by the node process
  external: number; // Memory allocated to external parts of the runtime, C++ objects ect
  rss: number; // resident set size: the total memory allocated to the node process
  traceDateTime: number; // unix timestamp from the trace
  traceKey: string; //hash of the unix timestamp at init used to identify all traces from the same run.

Example:

import { init, traceMemory, exportTraceToCSV, exportTrace, TraceMemoryUnit, traceBlock} from "ts-mem-trace";
const array = [];
init(TraceMemoryUnit.KiloByte);
traceMemory("0");
traceBlock("test-block", () => {
  for (let x = 0; x < 1000; x++) {
    array.push(x);
  }
});
traceMemory("1");
const records = exportTrace();
if (records != undefined) {
  records.forEach((item) => {
    console.log("name: " + item.recordName + " heapUsed: " + item.heapUsed);
  });
}
name: 0 heapUsed: 3833.8046875
name: test-block-block-start heapUsed: 3813.5390625
name: test-block-block-end heapUsed: 3856.65625
name: 1 heapUsed: 3819.890625
  • todo:
    • split this up into multiple files.
    • move export code from.
    • add custom record export support.
    • add tree based tracing so data can be associated to a stack allowing for flame graphs and the such.
    • implement a version that exports the data via http so tracing can be done on machines without disk access (Lambda ect)