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

build-start-rebuild-perf

v0.3.0

Published

Measures web app performance metrics: - Dev server startup time - Time to first paint - Time to app load (waiting for an element selector) - Reload time after a file changes

Readme

build-start-rebuild-perf

Measures web app performance metrics:

  • Dev server startup time
  • Time to first paint
  • Time to app load (waiting for an element selector)
  • Reload time after a file changes

Thanks to Discourse for providing inspiration for this script.

Usage

pnpm dlx build-start-rebuild-perf [options]

Example

# assuming running in an Ember project with a <img class="logo" /> in the app layout
pnpm dlx build-start-rebuild-perf --file "app/router.js" --wait-for ".logo"

Options

	-u, --url <url>                   URL to load (default: "http://localhost:4200")
  -f, --file <path>                 File to touch to trigger a reload (no default, but app/router.js is an option)
  -c, --command <cmd>               Command to start dev server (default: "pnpm start")
  -w, --wait-for <selector>         Element selector to wait for (default: "body")
  -t, --timeout <timeout ms>        number of ms to wait for the server to become ready (default: "120000")
  --page-load-timeout <timeout ms>  number of ms to wait in the browser for the pageload event (default: "60000")
  -l, --log-level <level>           Set the log level (choices: "log", "warn", "error")
  -h, --help                        display help for command

Example Output

# Performance Results

| Dev Server Ready | First Paint | App Loaded | Reload after change |
| ---------------- | ----------- | ---------- | ------------------- |
| 5,523 ms         | 5,618 ms    | 6,142 ms   | 918 ms              |

Share with us

Assuming you're in an Ember project and wondering if moving to Vite from the old Ember CLI is worth it, here's how you can use the script to create useful numbers:

  1. Start on your main branch or anywhwere you're still using Ember CLI with Webpack and Embroider
  2. Clear all caches (browser, build, etc) and remove your node_modules
  3. Run pnpm install to reinstall dependencies
  4. Run build-start-rebuild-perf once to get numbers for a cold start
  5. Run build-start-rebuild-perf again to measure a warm start
  6. Move to your vite branch where you enabled the new Vite based Embroider
  7. Repeat steps 2-5.

Share a your results with the Ember Initiative via email, or Mastodon, or Bluesky.


License

This project is part of the Ember Initative. It is developed by and © Mainmatter GmbH and contributors. It is released under the MIT License.