bobsingor

5 ms·

1. 31.▲
   by bobsingor 1y ago

   Yeah, that’s true. It is not doing vectorized rendering, so printing is bitmap-based like pdf.js. For most use cases it works fine, but I get that for more high-end printing it could be a limitation. It is not something I am focusing on rig
2. 32.▲
   by bobsingor 1y ago

   Thanks, really appreciate that. Definitely give it a try on your next project! I tested it on Chrome, Safari, and Edge, and it’s been working great across all of them.
3. 33.▲
   by bobsingor 1y ago

   Yeah, I was surprised too. Rendering actually feels even faster on my iOS device at high zoom than on desktop Chrome. It’s pretty fascinating. I’m currently working on annotations, highlights, comments, and more. Made good progress and shou
4. 34.▲
   by bobsingor 1y ago

   Quick update: I just added a new option where you can set a custom wasmUrl when initializing the snippet. This way you can host your own .wasm build if you want to be 100% sure it hasn’t been modified. Here’s the commit: https://
5. 35.▲
   by bobsingor 1y ago

   Good question. You can fully reproduce the build. We have a Dockerfile here that handles the process: https://github.com/embedpdf/embed-pdf-viewer/blob/main/packa... Also, if you look in the package.json
6. 36.▲
   by bobsingor 1y ago

   Thanks so much, that’s a huge compliment, really appreciate it. Actually, most of what you’re describing is already there. We built a tiling plugin ( https://github.com/embedpdf/embed-pdf-viewer/tree/main/
7. 37.▲
   by bobsingor 1y ago

   Thanks! I’ll be adding clearer documentation soon on how to integrate it with React and other major frameworks. The viewer is designed to be framework-agnostic, and I’m working on lightweight integration layers for React, Vue, Svelte, etc.
8. 38.▲
   by bobsingor 1y ago

   Thanks! Really appreciate that — curious to hear how it works out for you. As for size (gzipped): the main JS file is about 77kB, the web worker is around 43kB, and the largest part is pdfium.wasm at roughly 2.7MB. The wasm handles all the
9. 39.▲
   by bobsingor 1y ago

   Thanks! Yeah, I really get that, pdf.js gave me a ton of headaches too. Honestly, that’s part of why I started building this. I just needed something that didn’t fight me every step of the way. Not planning to build a PDF generator just yet
10. 40.▲
    by bobsingor 1y ago

    Thanks!
11. 41.▲
    by bobsingor 1y ago

    Wow, that really means a lot coming from you! I’ve come across SimplePDF quite a few times while researching! Super impressed by what you’ve built. Thanks for the kind words, fellow PDF’er
12. 42.▲
    Show HN: Open Source PDF Viewer Using Chrome’s PDF Engine (MIT, WebAssembly)(embedpdf.com)

    27 points by bobsingor 1y ago|26 comments
13. 43.▲
    by bobsingor 1y ago

    I just open-sourced EmbedPDF, a modern JavaScript PDF viewer that uses PDFium compiled to WebAssembly — not PDF.js. If you've ever tried to deeply customize PDF.js or needed high-fidelity rendering, you’ve probably hit its limits. And
14. 44.▲
    by bobsingor 4y ago

    Wow this worked! Your amazing! Thank you so much
15. 45.▲
    by bobsingor 4y ago

    Yes, i'm also done with Heroku. What alternative do you recommend?