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

@bazel/benchmark-runner

v0.1.0

Published

iBazel Benchmark Runner

Downloads

202

Readme

iBazel Benchmark Runner

This script runs iBazel on a specified target with the iBazel profiler enabled. After the initial build completes, it modifies a specified file by adding a newline to the end of it. The script reports the initial build time and the incremental build RTT.

It can also optionally launch chrome to a specified URL and report on the browser load RTT if the target (such as ts_devserver) serves a website.

Reporting

The scripts outputs the RTT in ms as follows:

[ibazel-benchmark-runner] Initial build time 24059ms
[ibazel-benchmark-runner] Incremental build RTT 4192ms
[ibazel-benchmark-runner] Browser load RTT 4402ms

Usage

node_modules/.bin/ibazel-benchmark-runner <run_target> <file_to_modify> [--url=<url>] [--initial_timeout=<seconds>] [--incremental_timeout=<seconds>]

| Argument | Description | | ------------- | ------------- | | run_target | The bazel target to run. | | file_to_modify | The file to modify in order to start in incremental build (a newline will be added to the end of this file). | | url | Url for the benchmark to navigate to in order to measure browser interactive RTT for incremental build (optional). | | initial_timeout | Maximum time to wait for the initial build (defaults to 300 seconds). | | incremental_timeout | Maximum time to wait for the incremental build (defaults to 60 seconds). | | browser_timeout | Maximum time to wait for browser page load event (defaults to 60 seconds). |

For example:

node_modules/.bin/ibazel-benchmark-runner //src:devserver src/foo/bar.ts --url=http://localhost:5432