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

weight

v0.2.0

Published

weight tells you the memory usage and loading time of your module

Downloads

10

Vulnerabilities

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

Links

Git

Maintainers

swatinemswatinem

Keywords

Readme

weight

weight tells you the memory usage and loading time of your module. Inspired by https://gist.github.com/isaacs/5733238

So read up on Unix Philosophy and node.js and make sure to write small modules that do just one thing but do that well.

Remember people, this is not Java. Your modules are not supposed to take 1 minute to start and use > 2G right after startup.

Installation

$ npm install weight

Usage

$ cd yourmodule
$ weight # current directory
load time: 25.723ms
js heap usage: 640.8kb
$ weight node_modules/mocha # relative directory
load time: 28.119ms
js heap usage: 806.2kb
$ weight /usr/lib/node_modules/weight/node_modules/bytes # absolute directory
load time: 0.636ms
js heap usage: 6.59kb

Caveat

  • loading time incurrs IO, so make sure your caches are warm!
  • heap usage uses process.memoryUsage().heapUsed internally, so it depends a lot on GC behavior. I actually had situations where it reported negative numbers, haha. So use this with caution!