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

nodeperf

v0.0.0

Published

Node runtime performance analyser

Downloads

3

Readme

(People who see this, nodex64 are debug binaries for node which you need to build yourself. Debug build is required. I will add more elaborate instructions later).

Example:

$ nodex64 ./src/run.js test.js
In total 50 (10 unique) optimizations were done taking 0.80 seconds of compiler time.

Found 11 issues.

Critical (3):

    - Function `doPhase` was hard deoptimized 11 times:
        1. At bailout position 2 an assumption failed: Expected a value not to be an integer. (check-non-smi)
        2. At bailout position 4 an assumption failed: Expected a value to be an integer. (check-smi)
        3. At bailout position 2 an assumption failed: Expected a value to be an integer. (check-smi)

    - Function `disabled` cannot be optimized because it contains a switch-statement that has case clauses that are either not integer literals or string literals
    - Function `doPhase` cannot be optimized because it has been reoptimized too many times.

High (6):

    - Function `THISISTHEFUNCTION` was hard deoptimized 4 times:
        1. At bailout position 14 an assumption failed: Expected a value not to be an integer. (check-non-smi)
        2. At bailout position 10 an assumption failed: Expected integer division operation not to be passed a 0 dividend, negative zero, not to overflow signed int32 range or have a non-zero remainder. (div-i)
        3. At bailout position 8 an assumption failed: Expected an object to have a certain hidden class. (check-maps)
        4. At bailout position 1 an assumption failed: Expected numeric property access not to be made out of bounds. (bounds-check)

    - The small function `noInline2` when called from the function `MissingInlineOpportunities` cannot be inlined because the former creates closures.
    - The small function `ClosureClass` when called from the function `redefinitionAbuse` cannot be inlined because the former creates closures.
    - The small function `redefinitionAbuse` when called from the function `[anonymous]` cannot be inlined because they do not share the same scope.

    - The function `ClosureClass.setAge` was re-defined at least 152 times.
    - The function `ClosureClass.getAge` was re-defined at least 152 times.

Medium (2):

    - The function `[anonymous]` when called from the function `MissingInlineOpportunities` cannot be inlined because they do not share the same scope.
    - The function `[anonymous]` when called from the function `[anonymous]` cannot be inlined because they do not share the same scope.

Low (0):