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

11ty-fx-profiler

v1.0.0

Published

Visualize how Eleventy spends its time using markers in the Firefox Profiler.

Downloads

4

Readme

11ty-fx-profiler

Visualize how Eleventy spends its build time using markers in the Firefox Profiler.

Usage

npm install 11ty-fx-profiler, then in your .eleventy.js (or eleventy.config.js) file, add:

  • at the top: import Profiler from '11ty-fx-profiler';
  • in your code, to install the profiler: Profiler(eleventyConfig);. Put this as the first line of the fonction that takes eleventyConfig as a parameter. To avoid losing data, the profiler needs to be installed before anything else calls into eleventyConfig.benchmarkManager.

This profiler will do nothing unless the PROFILE environment variable is set when running eleventy.

Possible values for the environment variable:

  • open: this will open the profile in a new tab in your default browser. This is the best for profiling during local development.
  • stdout: this will dump the entire profile JSON into the build log. Might be useful to profile what's happening when deploying.
  • any other value will be treated as a file name, and the profile will be saved to a file with that name.

For example, assuming you use yarn build to build your Eleventy website, you would use PROFILE=open yarn build to see a profile of it.

Adding more markers

The data already recorded by eleventy will be included, but it might be useful to include extra information for parts of your own code that could take time.

For example, if you have your own shortcode that you would like to instrument:

  eleventyConfig.addShortcode("shortcodename", async function(string) {
    let bench = eleventyConfig.benchmarkManager.get("User").get("> shortcodename > " + string);
    bench.before();
    /* ... */
    bench.after();
    return result;
  });