3 ms·

I've been working on an internal tool for my company using the same library. It's saved me a ton of work, but my experience has been similar to yours. I've even

I've been working on an internal tool for my company using the same library. It's saved me a ton of work, but my experience has been similar to yours. I've even had to lock in to a much older version for want of putting a lot more work on my plate since the API seems to have changed a fair bit. (well, between it and JSDOM which I am using to some rendering on the server). And like you I've had to write a bunch of the bindings/definitions myself or just reduce them to nil (declare module "yadda/yadday/thing" as any)—which is thankfully permissible since it just needs to be built once and run "forever" with near-zero need for feature additions, etc. All to extract images in a routine fashion. Just the same, I'm still immensely thankful they've published the library as OSS.

exikyut 6y ago
I'm benignly curious how pdfimages explodes in your use case.
- 52-6F-62 6y ago
  Unfortunately, it and Poppler, and Imagemagick, etc were all off the table. I was confined to running everything within a Node instance. Couldn't make calls out to command line tools. I tried probably 20 ways of using Poppler-based libraries to no avail. It definitely would have been the better performing route, and simpler to implement. As it is, since the app is low traffic for actual processing of the images it doesn't matter too much, thankfully. This library was helpful: https://github.com/ScientaNL/pdf-extractor https://github.com/ScientaNL/pdf-extractor I haven't had time to do it cleanly, but I should contribute back with the types I wrote after cleaning them up...