bvaughn

react-virtualized

TypeScript2016–2025

bvaughn / react-virtualized

react-virtualized

React components for efficiently rendering large lists and tabular data

Explore on GitHub Read Hacker News discussions

20Distinct people

20Mentions

0Explicit recommenders

27.1KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

React components for efficiently rendering large lists and tabular data

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

bvaughn/react-window · linked in 4 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year20 dated mentions

Observed mentions: 2016-07-11 09:54:51 UTC to 2025-08-11 16:08:02 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	3	3
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	5	5
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	1	1
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	3	3
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	3	3
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	1	1
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	3	3

What Hacker News says

5 sources

TheAceOfHearts·Jun 2, 2017

All of your points are incorrect. - Web does have access to the camera. I regularly upload images to the Facebook mobile site. You can also do live previews of images and allow users to experiment with filters before uploading. - Live streaming on mobile web is also possible. If you support DASH and HLS you can reach the vast majority of mobile users [0] - It's possible to support offline apps with mobile web, but it's definitely tricky. The biggest issue for most people is that you can't perform work in the background. Service workers are an attempt at improving on that. But you can still save data in localStorage or IndexedDB and push it up when the user reconnects. There's an offline and online event you can hook into. - Native apps aren't magical. If you're dealing with large collections on the web you can also virtualize em, look at

Read the rest

react-virtualized for an example [1]. That lets you avoid having to create as many DOM nodes all at once. - You can achieve the same thing by writing your web app as a shell that later loads additional content. That way the initial load feels faster. Check out Progressive Web Apps to see the direction that's headed. - Mobile web apps usually use JSON too. Nothing special about native apps here. - Both DASH and HLS fully support dynamic quality. Heck, DASH literally means "Dynamic Adaptive Streaming over HTTP". By supporting both you can target most mobile web browsers. Native apps use these same protocols. It's already implemented by the browser vendor or by native APIs. - You can jump to the middle of a video stream on mobile web. It's exactly the same as with a desktop browser. Go open up YouTube and skip a few minutes ahead. [0] https://developer.mozilla.org/en-US/Apps/Fundamentals/Audio_... [1] https://github.com/bvaughn/react-virtualized

In Is 2017 the beginning of the end for the app economy?

acemarke·Apr 20, 2017

There's also toolkits like React-Virtualized: https://github.com/bvaughn/react-virtualized .

In Proposal to start a new implementation of Thunderbird based on web technologies

wizardtrees·Apr 8, 2017

Check out React Virtualized. I have used it with great success and large datasets. https://bvaughn.github.io/react-virtualized/#/components/Lis... https://github.com/bvaughn/react-virtualized

In ReactXP – A library for building cross-platform apps

kevinwuhoo·Apr 4, 2017

+1 for React-Virtualized as well. FYI: there was a new "MultiGrid"[1] high level component that was added in 8.9.0 [2] which helps facilitate fixed columns/rows with less boilerplate. Though, nearly every time I've used the MultiGrid component, I've found myself eventually dropping back to ScrollSync + Grids/Lists. As the product grows in complexity, adding more complex interactions to MultiGrid is difficult as it doesn't expose all of the Grid API. [1]: https://bvaughn.github.io/react-virtualized/#/components/Mul... [2]: https://github.com/bvaughn/react-virtualized/blob/master/CHA...

In Show HN: React-data sheet, Excel-like spreadsheet component

bombtrack·Feb 20, 2017

Did you evaluate or consider react-virtualized [0]? I've used it for one internal app that loaded a couple thousand rows and it worked well. I don't think it meets all your requirements out of the box though, but it seems like the best option to build extensions for going forward. The creator Brian Vaughn was recently hired by Facebook, and also just finished work on v9 that is React Fiber compatible. For others that want a comparison, here's a writeup that explores the pros/cons of various React grid/table libs [1]. [0]: https://github.com/bvaughn/react-virtualized [1]: https://techblog.commercetools.com/advanced-data-tables-in-r...

In Show HN: Griddle 1.0 – A customizable datagrid component for React