Update version in NPM

[tquetano-r7]

Title says it all ... npm is currently set to v1.0.272, and according to git the newest release is v1.1.135 (for some time now). There is another issue related to an Unexpected Token semicolon, but I'm hoping the update will solve it, else I'll create a different issue.

[gabrielenosso]

+1! Current version is unusable (minimized version has an error: unexpected Token semicolon)
It could also be a good idea to add the debug version of the code (useful under dev)

[MrRio]

1.1.135 is a prerelease, still needs some testing. Does this work better for you?

https://github.com/MrRio/jsPDF/releases/tag/1.1.135

[gabrielenosso]

I'm using it with Webpack, and it doesn't work at all.
The npm version give the "unexpected token" error, while the 1.1.135 it's not imported correctly.
To let it work you have to first apply this fix (Flamenco@ef47c09); and then you have to export the jsPDF function (so adding at the end of the file "module.exports = jsPDF").

This is a great lib, that's why we need a way to use it through bundlers :D

[tquetano-r7]

@gabrielenosso hit it on the head, I was requesting the update in version to actually solve the exact problem he described with Webpack. If you can incorporate his fix and export recommendation (which is the CommonJS practice), I would be incredibly appreciative. We are craving the usage of this library desperately, but the breakage in Webpack is the sole roadblock.

[grofit]

👍

[flieks]

yes also would love an update that fixes the issues :)

[Avarga954]

Please update NPM this is a blocking issue for me as well.

[m-a-r-c-e-l-i-n-o]

+1

[thedamon]

+1. unusable with webpack :/

Is there any npm command I can run to install a working version?
Or a fork someone has made that works?

[pavestru]

For a workaround (but not really a solution) see this comment.

[grofit]

any news on this its been AGES and still no update

[cyberco]

Still no way to use it with WebPack? Will it ever be fixed? It's been over 8 months now.

[MrRio]

I'll get this sorted this week!
On Sun, 21 Feb 2016 at 21:59, cyberco notifications@github.com wrote:

Still no way to use it with WebPack? Will it ever be fixed? It's been over
8 months now.

—
Reply to this email directly or view it on GitHub
#549 (comment).

James Hall
Director
Parallax Agency Ltd
M. 07894950320

[cyberco]

@MrRio That would be great, the sooner the better since I really need a way to generate PDF's clientside (using webpack) and none of the other frameworks work either. Would be cool for jsPDF to be the first.

[cyberco]

I'm now using this trick, but that means I have to use v0.9.1 which prevents me from using jspdf-autotables. Any progress yet? I'm really waiting for this.