Gathering detailed insights and metrics for gatsby-plugin-why-did-you-render-redux
Gathering detailed insights and metrics for gatsby-plugin-why-did-you-render-redux
Gathering detailed insights and metrics for gatsby-plugin-why-did-you-render-redux
Gathering detailed insights and metrics for gatsby-plugin-why-did-you-render-redux
npm install gatsby-plugin-why-did-you-render-redux
Typescript
Module System
53.3
Supply Chain
80.7
Quality
75.1
Maintenance
100
Vulnerability
99.6
License
TypeScript (100%)
Total Downloads
45,291
Last Day
86
Last Week
385
Last Month
1,607
Last Year
27,566
1 Stars
14 Commits
2 Watching
6 Branches
1 Contributors
Minified
Minified + Gzipped
Latest Version
0.2.1
Package Id
gatsby-plugin-why-did-you-render-redux@0.2.1
Unpacked Size
14.47 kB
Size
5.15 kB
File Count
19
Cumulative downloads
Total Downloads
Last day
50.9%
86
Compared to previous day
Last week
3.2%
385
Compared to previous week
Last month
-2.1%
1,607
Compared to previous month
Last year
385.2%
27,566
Compared to previous year
7
1
Include the @welldone-software/why-did-you-render library when running gatsby develop
. It includes support for tracing useSelector
in your redux store.
Using npm:
npm i gatsby-plugin-why-did-you-render-redux
Using yarn:
yarn add gatsby-plugin-why-did-you-render-redux
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:
1{ 2 // ... 3 plugins: [ 4 { 5 resolve: 'gatsby-plugin-why-did-you-render-redux', 6 options: { 7 trackAllPureComponents: true, 8 trackUseSelector: true, 9 }, 10 }, 11 // ... 12 ], 13 // ... 14}
1{ 2 // ... 3 plugins: [ 4 { 5 resolve: 'gatsby-plugin-why-did-you-render-redux', 6 options: { 7 include: ['MyComponent', 'MyOtherComponent'] 8 }, 9 }, 10 // ... 11 ], 12 // ... 13}
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
8 existing vulnerabilities detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/10 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-12-16
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More