React Virtuoso is a simple, easy to use React component made to render huge data lists. Out of the box, Virtuoso:

• Handles gracefully variable sized items; no manual measurements or hard-coding of item heights;
• Automatically handles content resizing;
• Can optionally render footer at the end of the list;
• Supports pinning of the first N items to the top of the list.

To see live examples, check the storybook.

Install the package in your React project:

npm install react-virtuoso

Or, if yarn is your thing:

yarn add react-virtuoso

Then, put the component somewhere in your tree:

import * as React from 'react'
import * as ReactDOM from 'react-dom'
import { Virtuoso } from 'react-virtuoso'

const App = () => {
  return (
    <Virtuoso style={{ width: '200px', height: '400px' }} totalCount={200} item={index => <div>Item {index}</div>} />
  )
}

ReactDOM.render(<App />, document.getElementById('root'))

The component accepts an optional footer render property, the contents of which are rendered at the bottom of the list. The footer can be used to host a "load more" button or an indicator that the user has reached the end of the list.

<Virtuoso
  style={{ height: '300px', width: '500px' }}
  totalCount={100}
  item={Item}
  footer={() => <div>-- end reached --</div>}
/>

Check the footer, load more and endless scrolling examples for practical applications of the footer.

The component accepts an optional topItems property, that specifies how many of the items to keep "pinned" at the top of the list.

<Virtuoso style={{ height: '500px', width: '500px' }} topItems={2} totalCount={100000} item={Item} />

Check the fixed top items example for a live version of the above.

Several factors affect the component performance, the most important being the size of the visible area. Redrawing large items takes more time and reduces the frame rate. To see if this affects your case, change the component style property to something like {{width: '200px'}} and see if the frame rate gets better.

Next, if the content in the item prop is complex / large, use React.memo.

You can experiment with the overscan property which specifies how much more to render in addition to the viewport visible height. For example, if the component is 100px tall, setting the overscan to 150 will cause the list to render at least 250px tall content. In a nutshell, increasing the overscan causes less frequent re-renders, but makes each re-render more expensive (because more items will get replaced).

Loading images and displaying complex components while scrolling can cause hiccups and frame skips. To fix that, you can hook to the scrollingStateChange callback and replace the complex content in the item render prop with a simplified one. Check the scroll handling example for a possible implementation.

Finally, as a last resort, you can speed up things by hard-coding the size of the items using the itemHeight property. This will cause the component to stop measuring and observing the item sizes. Be careful with that option; ensure that the items won't change size on different resolutions.

Mandatory. Specifies the total amount of items to be displayed by the list.

Mandatory. Specifies how each item gets rendered. The callback receives the zero-based index of the item.

Optional; most often, you will need to tweak the size of the component by setting width and height. The style is passed to the outermost div element of the component.

Optional. Defines content to be rendered at the bottom of the list.

Optional. Causes the component to render extra content in addition to the necessary one to fill in the visible viewport. Check the Tweaking Performance section.

Gets called when the user scrolls to the end of the list. Receives the last item index as an argument. Can be used to implement endless scrolling.

Gets called when the user starts / stops scrolling. Can be used to hide complex item contents during scrolling.

Can be used to improve performance if the rendered items are of known size. Setting it causes the component to skip item measurements. See the Tweaking Performance section for more details.

CSS margins in the content are the Kryptonite of Virtuoso's content measuring mechanism - the contentRect measurement does not include them.

If this affects you, the total scroll height will be miscalculated, and the user won't be able to scroll all the way down to the list.

To avoid that, if you are putting paragraphs and headings inside the item, make sure that the top / bottom elements' margins do not protrude outside of the item container.

<Virtuoso
  totalCount={100}
  item={index => (
    <div>
      <p style={{ margin: 0 }}>Item {index}</p>
    </div>
  )}
/>

Virtuoso uses position: sticky to keep the virtual viewport at top of the scroller. This does not work in IE 11. Please open an issue (or even, PR) if you need this - it should be possible to implement a fallback mechanism using position: absolute.

Petyo Ivanov @petyosi

MIT License.