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

will-it-optimize

v0.1.1

Published

Suite of tests for determining what v8 will optimize

Downloads

4

Readme

will-it-optimize

Current Version

I don't care if something will blend (well, I kind of do). I want to know if something can be optimized by v8. will-it-optimize reports whether or not a function can be optimized based on its contents. Hopefully, this will make it easier to track what can be optimized in various versions of node.js without paying extremely close attention to the v8 codebase.

Running the Tests

npm start

Test Structure

A test is defined by the module.exports object. The following properties are supported:

  • description - String. A written description of the test. Markdown is allowed.
  • exec - Function. The test code to execute.
  • args - Optional Array. Arguments passed to the test code.
  • warmup - Optional Array. Array of objects used to warmup v8. If warmup is not specified, the test function will be invoked once using args as the arguments. Each object in the array results in an invocation of the test function. This is used to fill in v8's type info. Each object may contain the following fields:
    • args - Optional Array. Arguments passed to the test code on the given warmup iteration.

An example test is shown below. This will execute a function containing a with statement, which v8 cannot currently optimize.

module.exports = {
  description: '`with` statement',
  exec: function exec() {
    with ({}) {}
  }
};

Required Reading