Introducing Socket Firewall: Free, Proactive Protection for Your Software Supply Chain.Learn More
Socket
Book a DemoInstallSign in
Socket

build-start-rebuild-perf

Package Overview
Dependencies
Maintainers
1
Versions
8
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

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

latest
Source
npmnpm
Version
0.3.0
Version published
Maintainers
1
Created
Source

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:

  • Start on your main branch or anywhwere you're still using Ember CLI with Webpack and Embroider
  • Clear all caches (browser, build, etc) and remove your node_modules
  • Run pnpm install to reinstall dependencies
  • Run build-start-rebuild-perf once to get numbers for a cold start
  • Run build-start-rebuild-perf again to measure a warm start
  • Move to your vite branch where you enabled the new Vite based Embroider
  • 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.

FAQs

Package last updated on 25 Aug 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts