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

react-performance

v0.0.5

Published

Helpers to debug and record component render performance

Downloads

190

Readme

React Performance 🚀

Helpers to debug and record component render performance

With the release of React Fiber in v16, react-addons-perf has officially become obsolete. This project aims to be a "close enough" alternate solution.

Logs

Reports

Timing

Installation

  • Yarn: yarn add react-performance
  • npm: npm install react-performance

Usage

import ReactPerformance from 'react-performance'

You can also choose to import selectively:

import { measure, startRecording, printRecording } from 'react-performance'

NOTE: In a production environment, ReactPerformance disables itself.

Measure

To measure the rendering of a component, wrap it with the measure HOC:

class MyComponent extends React.Component {/* ... */}

export default ReactPerformance.measure({
  getId: 'some_recognizable_identifier',
  Component: MyComponent,
  isCollapsed: false,
})

That's it. Now logs will print every time the component renders.

If you use Redux, read the section below on how to Use with Redux.

Options:
  • getId is a string or function that helps you uniquely identify each component being rendered in the logs.
    • As a string, if it is a key of the component's props, the key and value are both used. Otherwise it is used as a static value.
    • As a function, it receives props and returns a string.
  • isCollapsed is true by default.
    • This collapses the duration & diff logs when a component renders.

Record

To generate reports, start recording data by running:

ReactPerformance.startRecording()

And then print out the report by running:

ReactPerformance.printRecording()

This prints out a report on all the components being measured.

Use with Redux

connect

Only "smart" components should be measured since those are typically the components that respond to state changes (and usually the only components that significantly impact performance).

With the assumption that any data passed down to components is encapsulated in a top-level state, the most appropriate way to use this with Redux is to use ReactPerformance.connect:

class MyComponent extends React.Component {/* ... */}

export default ReactPerformance.connect({
  mapStateToProps,
  mapDispatchToProps,
  getId: 'some_recognizable_identifier',
  Component: MyComponent,
})

This is equivalent to ReactPerformance.measure - except it also connects the component to the Redux store.

createStore

To get measurements on the full duration across all component renders triggered by dispatching actions, a middleware is provided to create the store:

const enhancer = redux.compose(
  // ...All other middleware first
  // This must be the last one!
  ReactPerformance.createNotifier(),
)
const store = redux.createStore(rootReducer, enhancer)

This will log measurements in batches of rerenders caused by updates to the store:


© 2017 Amsul

Licensed under MIT