Use main pdfkit repo

[diegomura]

I'd like to remove pdfkit fork and start using https://github.com/foliojs/pdfkit again. I branched from this a long time ago for multiple reasons, so I'm not sure the lift here. It will mean for sure to add several changes in that repo, which I think it could benefit the entire community, but not sure yet what those are.

I'll keep this issue as a sort of umbrella issue where I'll capture all the differences and report progress as I tackle them. It will be a slow path.

• [ ] Dedupe png-js here
• [ ] Font classes
• [ ] Line wrapper missing on our fork. We don't really need this, but we will need to ship it if we unify
• [ ] Object class differences
• [ ] Add user units param to page in original repo
• [ ] Path file differences
• [ ] Reference file differences
• [ ] Security file differences
• [ ] Virtual fs missing
• [ ] Use jay-peg instea of jpeg-exif here
• [ ] EmbedImage method
• [ ] Add PDF/a mixins
• [ ] Text mixing multiple differences
• [ ] Add PageMode and PageLayout to pdfkit
• [ ] Multiple document class differences
• [ ] Remove node dep for loading default fonts

[wojtekmaj]

Hey, regarding png-js bit - consider pngjs too! See my comment: https://github.com/diegomura/react-pdf/issues/676#issuecomment-1930922597

[diegomura]

Thanks! Just took a quick look, and pngjs has node deps too, meaning I'll need to fork it as for now, or have them onboard on shipping a browser build. And also convince pdfkit to adopt this. Because pdfkit already uses png-js the path towards unifying this is shorter, but I'll check what would be more convenient

[kishaningithub]

@foliojs Can you kindly pitch in and add your thoughts here?