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

leakpair

v1.0.24

Published

Proactive memory leak repair in Single Page Applications

Downloads

36

Readme

LeakPair

Proactive repairing of memory leaks in Single Page Applications

Installation and Usage

  1. Since LeakPair is an npx command tool, the only requirement for running it is to ensure you have Node installed in your system. LeakPair support node versions >= 14.  

    • On Windows and Mac

      Visit the official Node website and follow the instructions for your OS. This will install the latest version of Node on your system. This will also install the Node Package Manager (npm) and the node packages executor (npx) on your system. Check their successful installation with node -v, npm -v, and npx -v respectively.  

    • On Linux based systems

      Use the command sudo apt install npm. This will automatically install node, npm , and npx. However, the installed node version will be v12.22.9, while LeakPair require at least version 14. For that, install a node version manager globally on your system: npm install -g n

      Now you can use n 14.0.0 to install the supported version. Note that you can replace this version with any version higher than 14,  including n latest

  2. Once the supported version of node is installed, you can run LeakPair with the command npx leakpair [path] where path is the absolute path of the repository or file that you wish to repair for memory leaks. Note that LeakPair only supports .js, .jsx, .ts and .tsx files. That is, if you provide the path to a repository, it will only filter and process files with these extensions.

  3. By default, LeakPair will log the memory leak and repair statistics directly in the CLI. However, if you wish to store it in a file format, you can provide an optional argument for the output path: npx leakpair [path-of-project-to-repair] [path-for-output]

Example npx leakpair /Users/arooba/roosterjs  /Users/arooba/Desktop In this case, an output.txt file will be generated containing the leaks and repair statistics of roosterjs, in the user's Desktop directory.

Example of LeakPair's output log in CLI