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

@mishguru/timmy

v1.5.0

Published

Find out which files take the longest to require

Downloads

4

Readme

Timmy

Find out how long it takes to require a file or node module

Timmy

Installation

$ yarn global add @mishguru/timmy

CLI Usage

--file [path to file]

Time a file

$ timmy --file ./index.js

--package [name of package]

Time a package from node_modules

$ timmy --package bluebird

--quiet

Don't time individual require's, just print out the total time it took to load the file/package.

This is more accurate, as it does not include the overhead Timmy adds when collecting statistics.

$ timmy --package bluebird --quiet

--min [time = 100]

Set the minimum amount of time (in ms) that a require must take for it to show up in the results. This is to improve performance - the lower the time, the more stats that need collecting - the longer it takes to run.

This defaults to 100ms.

$ timmy --file ./index.js --min 50

JS Usage

You can also use Timmy via a JS api

printStats (cwd)

Print out all the times for required files up to this point.

You should call it once, immediately after you have finished requiring all your files.

import timmy from '@mishguru/timmy'

import 'allthethings'

timmy.printStats()

restoreRequire

This restores require() to it's default behaviour.

import timmy from '@mishguru/timmy'

// this require will be timed
require('thing-one')

timmy.restoreRequire()

// this require will not be timed
require('thing-two')

resetTimer

import timmy from '@mishguru/timmy'

This resets the total timer to the current time.

import timmy from '@mishguru/timmy'

// do a bunch of stuff that you don't want to time ...

timmy.resetTimer()

// require the files you want to time

timmy.printStats()

setMinDuration

This sets the min duration to record. You should set this before you start requiring files.

import timmy from '@mishguru/timmy'
timmy.setMinDuration(0)