-
Notifications
You must be signed in to change notification settings - Fork 166
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
anchor is not defined #19
Comments
percollate --version |
node --version |
my global install was a bit bumpy, I had some ancient version of nodejs on my system, installed via sudo, I managed to upgrade using 'n', but puppeteer didn't like the sudo for |
Thanks for reporting! Indeed there was a bug with that version, which I had fixed in the meantime. Glad to hear it worked out in the end. I usually install node from with the macOS installer directly, having had trouble with both I've updated the Readme to reflect what I think is the correct way of upgrading to the latest version using yarn: yarn global upgrade --latest percollate I've tested with the example page and it works on [email protected], but it seems I still have to write a few more styles for everything on that page to show up correctly in the PDF. Will get back with updates! |
|
at ubuntu server of mine I've manually removed the apparently old install of 0.1.5 and did fresh install via yarn and voila: it just works! (after adding some missing libs for pupeteer using https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#chrome-headless-doesnt-launch) I like the idea very much as pdfs on my reader means much less distractions and is easy to carry around and slowly digest :), thank you! |
That's great to hear! I've added a Troubleshooting section to the README that points to the Puppeteer troubleshooting page, thanks for the pointer.
That was my thinking as well; I actually got the idea from browsing Simon Wardley's online book, and I wanted to see how the chapters would look when bundled into a single PDF. |
The text was updated successfully, but these errors were encountered: