would this be a standalone library

I created a complex Table component based on Grid of react-virtualized, I’m rewriting it now, and I’m not sure that should I use this library directly or wait for it being merged into react-virtualized as v10.

I love the simplicity of this library compare to react-virtualized, seems the original purpose of this repo is an api experimental for react-virtualized v10, I’m using some apis like onScrollbarPresenceChange from react-virtualized which are not available in this library, but I could implement them on my side if I choose to use this library. So I want to make sure what’s the future of this library.

[bvaughn]

This library will be released as react-window and will not be merged into react-virtualized. Initially, I considered releasing these API changes as version 10 of react-virtualized but decided against it because I don’t intend to support as many types of components (like Collection or Masonry) and I don’t want to make people choose between upgrading and losing functionality or staying on an old version.

I hope react-virtualized will continue to be maintained and released in parallel with this library, and I think there are some lessons learned here that could improve performance for react-virtualized- but that’s it.

Whether you should build on top of this or react-virtualized is up to you. I won’t promise to support all of the API surface for react-virtualized here (e.g. onScrollbarPresenceChange). I think the API surface for react-virtualized got too big and hard to maintain and I’d like to avoid that with this library.

Cheers!

[nihgwu]

Here it is, BaseTable with frozen rows and columns support and other features, but based on react-virtualized right now, I planed to migrate to use react-window in the next version I didn’t expect it would take so long to open source it (I’m a bit busy with other stuffs)