MPQChampApp VS react-virtual

Hall of Champions: I modified this application but converting some independent application state to derived state with the help of an original-Redux-like implementation of useReducer, which resulted in potential savings of tens of thousands of unnecessary DOM elements per page. The performance improvements from this change were rendered somewhat moot by a refactor that replaced a select input with a number input, saving even more tens of thousands of unnecessary elements on the first paint. More below about my next steps for this app!

Making some UI improvements and updating the seed database to reflect changes in the source game for my RPG tracking app

An entity in database terminology is a person, place, or thing. It will have some sort of identifier, a singular name, and will contain more than one instance of data. These attributes help us decide whether or not business logic should be a full-fledged entity. The application in question is a character tracker for the Marvel Puzzle Quest game (repo here), and I need two entities:

One thing to keep in mind is that React Hyper Scroller may not be the best for all use-cases. If it doesn't work for you, there are very cool alternatives like react-window, react-virtualized or react-virtual.

Enjoy this library? Try the entire TanStack! React Query, React Table, React Charts, React Virtual

"Unopiniated" is right, it means "this library doesn't force you to use it in a particular way", while headless is more specific to UI. I've actually seen it being used by some of the more popular libraries like react-table, react-virtual, and headlessui.

While trying to figure out how to implement a dynamic grid in react-virtual, I noticed an omission/clarification in the docs regarding one of the useVirtual properties, so that was an easy win PR!