Plans for the future

[Uzlopak]

Today we released finally a new version of jsPDF. After some "hick-up" we have now jsPDF v. 1.5.2 (which should have been 1.5.0, but this is life ;)).

So what are the plans for the future?

First of all, with any new release, we have the risk of having some new issues with backwards compatibility. So we will try to fix the a priori. So please report your issues.

But on the long run we will merge the jspdf fork from @yWorks and unite those two jsPDF-lines and have hopefully a better jsPDF.

Do you have any thoughts? complaints? hopes? Write them here.

Best Regards
Aras Abbasi

[whitymighty]

Hi, I am introducing myself to jsPDF.
I saw that I came in a very critical period of this great project. And, lucky me, I found that all
html-to-PDF plugins were recently marked as deprecated.
How is the new version handeling html conversion?

[alex2wong]

Any update on modular build of jsPDF ? hence we can scale down the bundle size when we only need part of core and plugins.

[Uzlopak]

@whitymighty

You can use in the new version the method .html

See the various examples in the folder examples/html2pdf

@alex2wong
hmm. Dont know.

[iamstiil]

Hi 😄
Is there any thought of migrating to Typescript or Babel with ES6+?

[Uzlopak]

Maybe for 2.0. And if I have to do it alone then probably in year 2020.

[Uzlopak]

Time to fix the issues and prepare a release for this week.

[mio991]

would you like help with a migration to typescript?

[Uzlopak]

I had a lot of Stress this month, I think I will be free next month.

[markim]

Hi,

Just wondering if you could provide an estimate on the release date for the next npm bump.

Until 1.5.4 (or whatever is next) build engines will fail at the improper file-saver dependency that was rolled back on January 1st.

Is it possible to release a smaller update fixing the production breaking dependency issue instead of bundling it together for the next release?

Thank you for your time and hard work.

[brennanyoung]

Accessibility is my number 1 request.

[moshiurse]

First of all. Thanks for you hard effort. Its made my life easy.
I request you to add Custom font support for Bengali Language.
I did't find any solution to support this language in JSPDF.
I searched in SO a lot but still got no response.
Thanks Again.

[mnemanja]

Hi, first off all, thanks for this awesome library!

I wanted to know what is happening with this project? Last release was a year ago in 2018.

Is this project still alive?

[github-actions]

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.

[brennanyoung]

It's perhaps worth mentioning that Chromium is getting 'print' to pdf/ua in the very near future.

https://blog.chromium.org/2020/07/using-chrome-to-generate-more.html

This means we will soon have a JS to (accessible) pdf pathway available in two major browsers (Chrome and Edge), and available to any web author.

Chromium can also run headless, which could be a solution for automated PDF production in many cases.

Personally, I am delighted about this announcement, and the forthcoming feature it heralds, but it is likely to make jsPDF (and similar utilities) less essential, perhaps even obsolete.

[HackbrettXXX]

@brennanyoung If I understand correctly, the Chromium PDF functionality only lets you output the current web page as PDF and add accessibility tags. JsPDF, however, has many other use cases like generating documents/tables from data or creating PDFs from SVG images. This is why I don't think the Chromium PDF functionality will make jsPDF obsolete.

[brennanyoung]

I'm glad you can see a future for jsPDF, because it's a very useful tool. My own focus is on accessibility, so until jsPDF supports this, I am on the lookout for any alternatives.

I haven't tried the chromium feature yet, but my understanding is that it converts HTML semantics and ARIA roles/attributes (if they are present) into PDF/UA tags. It wont fix things up if the markup is poor, or lacks semantics. Garbage-in, garbage-out.

Currently, if you print an HTML page to PDF, all semantic data is lost, no matter how carefully it was applied to the original markup.

However, with the new chromium feature, you could have an almost empty DOM with a javaScript that generates a data table (with appropriate semantics) and then you could generate a PDF from that. Other kinds of js-based document authoring could be imagined too. This is (I think) very close to the use cases you mention. SVG is a bit of wild card, though.

With that said, I expect the first chromium implementations to be less than perfect, or constrained in various ways. I'll be surprised if they get SVG working straight off the bat (not least because SVG accessibility is still in its infancy).

[github-actions]

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.

[esaesa]

Any updates?

[nzurita]

Hello @Uzlopak can we access docs for version 1.4 somewhere? Thank you

[saidalsaidi]

Wonderful library help to customize pages and reports with more flexibility, it will be better if there is ability to deal with large image as png, I have an issue of replacing base64 png in jsPdf pages

[andrewpking]

Will this repo be supported in the future? I'm having a hard time using ChartDetective which depends on this repo.