Gathering detailed insights and metrics for @john-osullivan/react-window-dynamic-fork
Gathering detailed insights and metrics for @john-osullivan/react-window-dynamic-fork
npm install @john-osullivan/react-window-dynamic-fork
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (97.47%)
CSS (2.39%)
HTML (0.14%)
Love this project? Help keep it running — sponsor us today! 🚀
Total Downloads
748,882
Last Day
1,089
Last Week
1,506
Last Month
15,536
Last Year
119,579
16,181 Stars
411 Commits
795 Forks
63 Watching
7 Branches
34 Contributors
Minified
Minified + Gzipped
Latest Version
1.9.0-alpha.1
Package Id
@john-osullivan/react-window-dynamic-fork@1.9.0-alpha.1
Unpacked Size
1.01 MB
Size
232.79 kB
File Count
28
NPM Version
6.9.0
Node Version
10.15.3
Cumulative downloads
Total Downloads
Last day
45.2%
1,089
Compared to previous day
Last week
-60.4%
1,506
Compared to previous week
Last month
27.8%
15,536
Compared to previous month
Last year
-47.1%
119,579
Compared to previous year
2
40
This fork of react-window
is published from issues/6 @ bc9192b
. I am publishing this fork in order to make the DynamicSizeList code available on npm, as installing directly from GitHub misbehaves in some CI/CD build environments. My only actual modification is the check-for-update.js
file which runs on build
. This is the full code of that file below; its only purpose is to check whether 1.9.0
(including an alpha version) has been published, exiting the process if it has.
1const npmApi = require('npm-api'); 2const semver = require('semver'); 3const process = require('process'); 4const npm = new npmApi(); 5const reactWindow = npm.repo('react-window'); 6 7reactWindow.package().then((pkgJson) => { 8 let version = pkgJson.version; 9 if (semver.satisfies(semver.coerce(version), '>=1.9.0')) { 10 throw new Error(`react-window ${version} has been released, please uninstall this fork and reinstall react-window.`); 11 } else { 12 console.log(`\nMost recent react-window version is ${version}, DynamicSizeList not yet available on npm.`); 13 console.log('This fork package will inform you when react-window @ 1.9.0 is available. \n') 14 } 15}).catch((err) => { 16 console.log(`\n${err}\n`); 17 process.exit(1) 18});
React components for efficiently rendering large lists and tabular data
1# Yarn 2yarn add react-window 3 4# NPM 5npm install --save react-window
Learn more at react-window.now.sh:
react-virtualized-auto-sizer
: HOC that grows to fit all of the available space and passes the width and height values to its child.react-window-infinite-loader
: Helps break large data sets down into chunks that can be just-in-time loaded as they are scrolled into view. It can also be used to create infinite loading lists (e.g. Facebook or Twitter).react-window
different from react-virtualized
?I wrote react-virtualized
several years ago. At the time, I was new to both React and the concept of windowing. Because of this, I made a few API decisions that I later came to regret. One of these was adding too many non-essential features and components. Once you add something to an open source project, removing it is pretty painful for users.
react-window
is a complete rewrite of react-virtualized
. I didn't try to solve as many problems or support as many use cases. Instead I focused on making the package smaller1 and faster. I also put a lot of thought into making the API (and documentation) as beginner-friendly as possible (with the caveat that windowing is still kind of an advanced use case).
If react-window
provides the functionality your project needs, I would strongly recommend using it instead of react-virtualized
. However if you need features that only react-virtualized
provides, you have two options:
react-virtualized
. (It's still widely used by a lot of successful projects!)react-window
primitives and adds the functionality you need. You may even want to release this component to NPM (as its own, standalone package)! 🙂1 - Adding a react-virtualized
list to a CRA project increases the (gzipped) build size by ~33.5 KB. Adding a react-window
list to a CRA project increases the (gzipped) build size by <2 KB.
Yes. I recommend using the react-virtualized-auto-sizer
package:
Here's a Code Sandbox demo.
If your list looks something like this...
...then you probably forgot to use the style
parameter! Libraries like react-window work by absolutely positioning the list items (via an inline style), so don't forget to attach it to the DOM element you render!
Yes. I recommend using the react-window-infinite-loader
package:
Here's a Code Sandbox demo.
Yes, using the outerElementType
prop.
Here's a Code Sandbox demo.
Yes, although it requires a bit of inline styling.
Here's a Code Sandbox demo.
Yes, although it requires a bit of inline styling.
Here's a Code Sandbox demo.
Yes, although it requires a small amount of user code. Here's a Code Sandbox demo.
MIT © bvaughn
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
Reason
Found 5/22 approved changesets -- score normalized to 2
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
Project has not signed or included provenance with any releases.
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
79 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-02-03
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