Open andreaslarssen opened 1 year ago
Hey there!
We can do that, but pdf-lib relies on:
"@pdf-lib/upng": "^1.0.1",
Both of them rely on pako 1...
Right... and both https://github.com/Hopding/standard-fonts/pull/2 and https://github.com/Hopding/upng/pull/1 are dead in the water...
How about forking the dependencies as well?
Ok, let's do that:
I'm currently working for a client that uses this package, so I would have to ask them about spending my time on the upng-package. As for the standard-fonts package, I would not be able to maintain this over time, so it seems like a bad idea for me to fork it. Maybe someone who's more invested in the package could do it?
Would your client be able to maintain it?
I really doubt that's going to happen
I just published a standard-fonts package with updated dependency, mind trying it out https://www.npmjs.com/package/@dineshsolanki/standard-fonts
@andreaslarssen @DineshSolanki Can someone open a PR on UPNG.js to upgrade pako, or at least open an issue explaining the problem? This way we don't need to open and maintain yet another fork.
Describe your idea
From https://github.com/Hopding/pdf-lib/issues/689:
How could this be implemented?
See above
What problem are you trying to solve?
See above
Why does this matter to you?
Optimization bailouts, and prevents us from upgrading to Angular 16 (?)
Would others find this helpful?
Yes
Are you interested in implementing your proposal?
No
Why are you submitting a proposal?
To keep the lib alive
Additional Notes
No response