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

v8-deopt-webapp

v0.5.0

Published

View the deoptimizations in a V8 log

Downloads

7

Readme

v8-deopt-webapp

Display the V8 optimizations and deoptimizations of a JavaScript file

Installation

Check out v8-deopt-viewer for a CLI that automates this for you!

npm i v8-deopt-webapp

Usage

  1. Generate a PerFileDeoptInfoWithSources object:

    1. Use v8-deopt-generate-log and v8-deopt-parser to generate a V8DeoptInfo object.

    2. Use the groupByFile utility from v8-deopt-parser to group the results by file.

    3. Extend the resulting object with the source of each file listed, and the shortened relative path to that file (can be defined relative to whatever you like)

      import { parseV8Log, groupByFile } from "v8-deopt-parser";
      
      const rawDeoptInfo = await parseV8Log(logContents);
      const groupDeoptInfo = groupByFile(rawDeoptInfo);
      const deoptInfo = {
      	...groupDeoptInfo,
      	// Define some addSources function that adds the `src` and `relativePath` property
      	// to each file object in groupDeoptInfo.files
      	files: await addSources(groupDeoptInfo.files),
      };
  2. Include the object in an HTML file

  3. Include dist/v8-deopt-webapp.css and dist/v8-deopt-webapp.js in the HTML file

  4. Call V8DeoptViewer.renderIntoDom(object, container) with the object and the DOM Node you want the app to render into

Currently, we only produce a UMD build, but would consider publishing an ESM build if it's useful to people

Contributing

See the Contributing.md guide at the root of the repo for general guidance you should follow.

To run the webapp locally:

  1. cd into this package's directory (e.g. packages/v8-deopt-webapp)
  2. Run node test/generateTestData.mjs
  3. Open test/index.html in your favorite web browser

By default, the test page (test/index.html) loads the data from test/deoptInfo.js. If you want to simulate a log that doesn't have sources, add ?error to the URL to load deoptInfoError.js.

If you make changes to v8-deopt-generate-log or v8-deopt-parser, you'll need to rerun generateTestData.mjs to re-generate deoptInfo.js & deoptInfoError.js.