-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Images not working #7
Comments
Hmm, it's kind of weird. Why did you even have to downgrade pdfkit? Running npm install should have downloaded the one from package.json. Looking at your prompt, I assume you've downloaded sources and run the image.js example from the examples directory. Have you changed anything? If you have - could you include the file? The docs will cover whole functionality by the end of next week (I'll do my best to finish it even earlier - maybe Wednesday) |
Hi, I did both, installed it using The I figured out that in
|
Hey, there's plenty of time till monday :) I'll take a look at it ;) Hold on |
You can have a look at my dirty workaround in my forked repository. |
Oh, I got it, pdfmake updates pdfkit in a few places. The npm version already contains these updates. To make it run from sources, you should call |
But the |
ooops, my mistake, sorry... I'll fix it in a second |
Great I gonna give it a try this week ;) You're a great programmer… |
thx ;) |
OK, it's fixed now, thanks for pointing it out. |
Great! Thanks. |
I've also upgraded pdfkit to the newest version 0.5.2, which means you shouldn't be using var doc = printer.createPdfKitDocument(docDefinition);
doc.pipe(fs.createWriteStream('file.pdf');
doc.end(); |
pdfkit 0.5.2 introduced another "bug" in browser-based pdfmake. If you're printing directly in the browser, wait for pdfmake 0.1.5. I'm working on it |
I'm using it server-side :-)
|
I'm really fighting with your missing documentation. I try to run the
images.js
-example, but it will give me the following error:I already tried downgrading
pdfkit
to version 0.2.7 which is declared inpackage.json
but it won't work. Where's the problem?The text was updated successfully, but these errors were encountered: