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

gatsby-plugin-why-did-you-render-redux

v0.2.1

Published

Gatsby plugin to include @welldone-software/why-did-you-render with useSelector tracing

Downloads

1,576

Readme

gatsby-plugin-why-did-you-render-redux

Include the @welldone-software/why-did-you-render library when running gatsby develop. It includes support for tracing useSelector in your redux store.

Installation

Using npm:

npm i gatsby-plugin-why-did-you-render-redux

Using yarn:

yarn add gatsby-plugin-why-did-you-render-redux

How To Use

This plugin allows for most options available in @welldone-software/why-did-you-render. include, exclude, and notifier aren't able to pass from gatsby-config.js to the plugin because Gatsby stringifies all plugin options. As a result, you can pass in include and exclude arrays as strings which will be used to construct simple new RegExp(string) instances. notifier is completely unsupported.

An additional option is added called trackUseSelector, which specifically targets tracing redux selectors as it requires a special step to configure. This means you don't need to add useSelector to trackExtraHooks.

You can set it up in your Gatsby project by adding it to gatsby-config.js like this:

{
  // ...
  plugins: [
    {
      resolve: 'gatsby-plugin-why-did-you-render-redux',
      options: {
        trackAllPureComponents: true,
        trackUseSelector: true,
      },
    },
    // ...
  ],
  // ...
}
{
  // ...
  plugins: [
    {
      resolve: 'gatsby-plugin-why-did-you-render-redux',
      options: {
        include: ['MyComponent', 'MyOtherComponent']
      },
    },
    // ...
  ],
  // ...
}