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

as-heap-analyzer

v1.2.0

Published

assemblyscript heap dump analysis tooling

Downloads

7

Readme

as-heap-analyzer

assemblyscript heap dump analysis tooling

How to use

  • install as-heap-analyzer
npm i -D as-heap-analyzer
  • Before you build assemblyscript to wasm, add --transform as-heap-analyzer/transform/addHeapAnalyzerInfo.mjs or add following line in asconfig.json
"transform": ["as-heap-analyzer/transform/addHeapAnalyzerInfo.mjs"]

for run assemblyscript in nodejs

  • run code and use analysis function
import { memory } from "../build/debug.js";
import { readFileSync } from "fs";
import { analysis } from "as-heap-analyzer/dist/index.js";
import assert from "assert";

const wasm = readFileSync("build/debug.wasm");
const memoryUsage = analysis(memory, wasm);
memoryUsage.forEach((v, k) => console.log(`${k} use ${v} bytes`));

for run assemblyscript in browser

  • run code and use analysis function
import { memory } from "./build/release.js";
import { analysis } from "as-heap-analyzer/dist/index.js";

const wasm = (await (await fetch(new URL("build/release.wasm", import.meta.url))).body.getReader().read()).value;
const memoryUsage = analysis(new Uint8Array(memory.buffer), wasm);
memoryUsage.forEach((v, k) => {
  document.body.innerText += `${k} use ${v} bytes\n`;
});

for run assemblyscript in other device (self-diagnosis)

  • use self-diagnosis API in assemblyscript to trace memory information to log
import { dumpUsedMemoryDetail } from "as-heap-analyzer/assembly/index";

trace(dumpUsedMemoryDetail());
  • run cli
npx as-heap-analyzer frame <transformed_wasm_module_path>
  • copy and paste self-diagnosis result from log to cli

  • the result should be:

total memory usage is 48300
  class ~lib/arraybuffer/ArrayBuffer use 544 bytes
  class assembly/index/A use 6400 bytes
  class ~lib/array/Array<assembly/index/A> use 48 bytes
  class assembly/index/B use 32 bytes