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.