Gathering detailed insights and metrics for react-virtualized
Gathering detailed insights and metrics for react-virtualized
Gathering detailed insights and metrics for react-virtualized
Gathering detailed insights and metrics for react-virtualized
@types/react-virtualized
TypeScript definitions for react-virtualized
react-virtualized-auto-sizer
Standalone version of the AutoSizer component from react-virtualized
@types/react-virtualized-auto-sizer
TypeScript definitions for react-virtualized-auto-sizer
esbuild-plugin-react-virtualized
ESBuild plugin for fixing react-virtualized
React components for efficiently rendering large lists and tabular data
npm install react-virtualized
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
26,436 Stars
1,990 Commits
3,062 Forks
227 Watching
25 Branches
200 Contributors
Updated on 28 Nov 2024
Minified
Minified + Gzipped
JavaScript (97.29%)
CSS (1.67%)
HTML (1.03%)
Cumulative downloads
Total Downloads
Last day
-3.9%
196,489
Compared to previous day
Last week
12.1%
1,098,021
Compared to previous week
Last month
5.6%
4,255,882
Compared to previous month
Last year
-35.7%
68,615,566
Compared to previous year
66
React components for efficiently rendering large lists and tabular data. Check out the demo for some examples.
The following wonderful companies have sponsored react-virtualized:
Learn more about becoming a sponsor!
react-window
If you're considering adding react-virtualized
to a project, take a look at react-window
as a possible lighter-weight alternative. Learn more about how the two libraries compare here.
Install react-virtualized
using npm.
1npm install react-virtualized --save
ES6, CommonJS, and UMD builds are available with each distribution. For example:
1// Most of react-virtualized's styles are functional (eg position, size). 2// Functional styles are applied directly to DOM elements. 3// The Table component ships with a few presentational styles as well. 4// They are optional, but if you want them you will need to also import the CSS file. 5// This only needs to be done once; probably during your application's bootstrapping process. 6import 'react-virtualized/styles.css'; 7 8// You can import any component you want as a named export from 'react-virtualized', eg 9import {Column, Table} from 'react-virtualized'; 10 11// But if you only use a few react-virtualized components, 12// And you're concerned about increasing your application's bundle size, 13// You can directly import only the components you need, like so: 14import AutoSizer from 'react-virtualized/dist/commonjs/AutoSizer'; 15import List from 'react-virtualized/dist/commonjs/List';
Note webpack 4 makes this optimization itself, see the documentation.
If the above syntax looks too cumbersome, or you import react-virtualized components from a lot of places, you can also configure a Webpack alias. For example:
1// Partial webpack.config.js 2{ 3 alias: { 4 'react-virtualized/List': 'react-virtualized/dist/es/List', 5 }, 6 ...rest 7}
Then you can just import like so:
1import List from 'react-virtualized/List'; 2 3// Now you can use <List {...props} />
You can also use a global-friendly UMD build:
1<link rel="stylesheet" href="path-to-react-virtualized/styles.css" /> 2<script src="path-to-react-virtualized/dist/umd/react-virtualized.js"></script>
Now you're ready to start using the components. You can learn more about which components react-virtualized has to offer below.
React Virtualized has very few dependencies and most are managed by NPM automatically.
However the following peer dependencies must be specified by your project in order to avoid version conflicts:
react
,
react-dom
.
NPM will not automatically install these for you but it will show you a warning message with instructions on how to install them.
By default all react-virtualized components use shallowCompare
to avoid re-rendering unless props or state has changed.
This occasionally confuses users when a collection's data changes (eg ['a','b','c']
=> ['d','e','f']
) but props do not (eg array.length
).
The solution to this is to let react-virtualized know that something external has changed. This can be done a couple of different ways.
The shallowCompare
method will detect changes to any props, even if they aren't declared as propTypes
.
This means you can also pass through additional properties that affect cell rendering to ensure changes are detected.
For example, if you're using List
to render a list of items that may be re-sorted after initial render- react-virtualized would not normally detect the sort operation because none of the properties it deals with change.
However you can pass through the additional sort property to trigger a re-render.
For example:
1<List {...listProps} sortBy={sortBy} />
Grid
and Collection
components can be forcefully re-rendered using forceUpdate
.
For Table
and List
, you'll need to call forceUpdateGrid
to ensure that the inner Grid
is also updated. For MultiGrid
, you'll need to call forceUpdateGrids
to ensure that the inner Grid
s are updated.
API documentation available here.
There are also a couple of how-to guides:
Examples for each component can be seen in the documentation.
Here are some online demos of each component:
And here are some "recipe" type demos:
react-virtualized aims to support all evergreen browsers and recent mobile browsers for iOS and Android. IE 9+ is also supported (although IE 9 will require some user-defined, custom CSS since flexbox layout is not supported).
If you find a browser-specific problem, please report it along with a repro case. The easiest way to do this is probably by forking this Plunker.
Here are some great components built on top of react-virtualized:
Use GitHub issues for requests.
I actively welcome pull requests; learn how to contribute.
Changes are tracked in the changelog.
react-virtualized is available under the MIT License.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 9/26 approved changesets -- score normalized to 3
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
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
111 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
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