andrewlu0

just added an example implementation in the xlsx viewer for search, but the code is yours to modify and customize. react-xlsx should expose the necessary functions to implement a custom search (by workbook/sheet etc...)

added some basic filtering/sort/search support, lmk what you think!

Hey! Very valid feedback - working on improving the file system component and overall site performance today

Responded above but the components like the file viewers should not depend on next. Please lmk if it gets pulled when installing via CLI

Thank you! Working on optimizing

Someone requested web components earlier so let me know if you make that happen!

Heard the performance feedback will work on it today!

Hey! Those components are used for the demo site, and shouldn’t ship or get installed when you install the components in the registry.

None of the ones in the registry should have next as a dependency, please lmk if otherwise

TIL those are called Miller columns !

Valid feedback a few other comments have mentioned , I’m going to try improving the home page tomorrow

We use react-pdf for the viewer which I believe uses pdf JS under the hood

We aren’t not trying to reinvent that engine, rather just provide a building block for people to plug in their design system to its controls

if you mean our docx viewer/editor specifically its hard to say without manually testing the visual fidelity with Word on some complex docx files

you are welcome to try it with your own documents and see, but its just one example we wanted to show. for the blocks that use the react-docx library, you can always copy the code and use a different method to render the docx file/thumbnails

it should be much faster on the individual component's page

the root page is a bit slow with all the viewers, in practice you probably wont have that many in your app on one page

coming back to this now and added it in a few places

on the demos - everything below the fold is lazy loaded but i will see what we can do to improve the mobile perf