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

miniprogram-probe

v0.1.0

Published

[![npm version][npm-version-src]][npm-version-href] [![bundle][bundle-src]][bundle-href] [![JSDocs][jsdocs-src]][jsdocs-href] [![License][license-src]][license-href]

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

octohashoctohash

Keywords

wechat-miniprogrammemorywatcher

Readme

miniprogram-probe

npm version bundle JSDocs License

Usage

miniprogram-probe samples WeChat Mini Program memory on a real Android device.

Requirements

  • Node.js and pnpm
  • Android device with WeChat installed
  • ADB

Install ADB:

On macOS, ADB is usually installed at:

~/Library/Android/sdk/platform-tools/adb

If adb is not found, add it to PATH:

echo 'export PATH="$HOME/Library/Android/sdk/platform-tools:$PATH"' >> ~/.zshrc
source ~/.zshrc

Enable USB debugging on the phone, connect it to the computer, then check:

adb devices

The device status should be device, not unauthorized or offline.

Usage

Install dependencies:

pnpm install

List devices:

pnpm start device

Open the target Mini Program and keep it in the foreground, then start sampling:

pnpm start watch

Set a custom interval and output file:

pnpm start watch --interval 1000 --output outputs/watch.json

Press Ctrl-C to stop. The CLI keeps writing JSON while sampling and prints the final result when stopped.

Process Selection

WeChat may keep several Mini Program processes alive:

com.tencent.mm:appbrand0
com.tencent.mm:appbrand1
com.tencent.mm:appbrand2

The CLI does not guess from appbrand0/1/2. It reads Android Activity state, finds the pid for the current AppBrandUI, then samples that pid with dumpsys meminfo.

To avoid sampling a background leftover process, open the target Mini Program in the foreground before running watch. To verify manually:

adb shell dumpsys window | grep -E 'mCurrentFocus|mFocusedApp'
adb shell dumpsys activity top | grep -A40 'ACTIVITY com.tencent.mm/.plugin.appbrand.ui.AppBrandUI'
adb shell ps -A | grep 'com.tencent.mm:appbrand'

Configuration

No config file is required.

Options:

  • --interval <ms>: sample interval. Default: 5000.
  • --output <file>: JSON output path. Default: outputs/miniprogram-probe-watch-<timestamp>.json.

Development

pnpm build
pnpm typecheck
pnpm lint
pnpm test

License

MIT License © jinghaihan