Super cool. Working on a local AI tool specifically for document workflow automation (where context = screen/web/folders/files), and this could come in super useful. I do most of the PDF/DOCX/etc. parsing natively in Rust, but having a nice way to see the output without spinning up Word or Powerpoint is a huge leap.
Using lopdf[1] for PDF parsing, rtf-parser[2] for RTF, calamine[3] for XLSX, and I'm sure you know that DOCX/PPTX/etc. is basically just a zip file of XML + text. The LLM cares about textual data (which just gets moderately cleaned up post-extraction), so I (thankfully) didn't have to deal with rendering. But showing a preview or end-result to a user would be a huge plus, so I can see myself using your library.
How is your PDF coverage? They are notoriously difficult things to render, with endless edge cases.
Mozilla’s PSD.js is the status quo here, so what do you do better than them?
By quirk of fate i've spent the past 2 days prototyping some stuff on pdfjs. Just trying to figure out a game plan for handling bounding boxes in the face of page zooming, different resolutions etc. etc. I can't see it mentioned whether the components are virtualising pages (as in reusing dom elements as document pages scroll by). I guess i just learned what i'll be exploring tomorrow then...
_Try_ to? Are you serious? We're not taking ambiguity due to phrasing, we're talking straight up not mentioning it on either the front page, on the show all page or even on the page the components button takes you to. Not even on this forum thread. There's barely any text on the front page to change and there are even multiple places you can mention React. You could mention it in the title, e.g. "Open source _React_ UI kit for modern document apps" or you could add it to the second paragraph, e.g. "React components ready to drop into user-facing flows, agents, or internal tools." Not to mention the components page. And given what you use to make the website, how does it take this long to update something this trivial when you are going out of your way to promote it, replying to comments and your other services by proxy?
Also, add either user interactive loading of components or lazy load the demos, the amount of demos murder performance on phones.
Cool project! I was playing around with the Excel viewer - the docs claim "Search across sheets and cell ranges", but I can't seem to trigger search functionality and the browser search bar can't find contents on cells.
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
thats fair and definitely something we can try supporting in the future. we started with React because of how familiar models are with shadcn and tailwind
we hope this can be useful for people building in React though!
Looks clean and works fine, but it needs optimization. Clicking "Type" in the "schema builder" example takes 1~2 seconds to open the popover in the landing page(macbook pro m4). I think its because there are lots of heavy components, but still it's too slow.
Thanks, that looks awesome! We were looking to add DOCX and XLSX preview to our app, and were planning to do server-side conversion to PDF (which seems to be what most other apps resort to) due to the lack of good libraries to render it, and this is exactly what we were looking for! :)
Hi! I'm one of the engineers at Extend that worked on this - one of our other engineers created a Rust XLSX/XLS parser that we ported to WASM to our @extend-ai/react-xlsx package which handles the rendering/charts. It exposes some hooks so users can use their own components for the toolbar
Thanks for releasing publicly.
[1] https://github.com/J-F-Liu/lopdf
[2] https://github.com/d0rianb/rtf-parser
[3] https://github.com/tafia/calamine
testing was mostly manual with a test corpus we generated. its not perfect but its pretty close for most files we've seen
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
By quirk of fate i've spent the past 2 days prototyping some stuff on pdfjs. Just trying to figure out a game plan for handling bounding boxes in the face of page zooming, different resolutions etc. etc. I can't see it mentioned whether the components are virtualising pages (as in reusing dom elements as document pages scroll by). I guess i just learned what i'll be exploring tomorrow then...
the zoom should work with the bounding box highlights, we're working on adding rotation support
Also, add either user interactive loading of components or lazy load the demos, the amount of demos murder performance on phones.
on the demos - everything below the fold is lazy loaded but i will see what we can do to improve the mobile perf
Is this a known issue?
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
we hope this can be useful for people building in React though!
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
i can't promise its visually 1:1 with Word/Excel but its pretty close on the corpus we tested with
could not have been easy
On mobile Safari…