Pdfkit VS puppeteer

Like the WickedPDF gem, the PDFkit gem uses wkhtmltopdf on the backend to convert plain HTML and CSS files into PDF documents.

In today's #10stips (where you learn how to solve coding issues within 10 seconds) we talk about the lovely PDFKit gem.

Alternatively, there tools like pdfkit if you want to build off HTML pages (and are happy to deal with wkhtmltopdf and it's older style CSS).

A couple of popular gems to convert HTML to PDF in Rails are PDFKit and WickedPDF. They both use a command line utility called wkhtmltopdf under the hood; which uses WebKit to render a PDF from HTML.

You could probably do it using something like Puppeteer [0].

[0]: https://pptr.dev/

Puppeteer

Just as described on the docs

Execution context was destroyed, most likely because of a navigation #3323

"page.waitForXPath is not a function" in 22.10.0

For more information, you can refer to the Puppeteer Documentation and BeautifulSoup Documentation.

I had to write my JavaScript code to display the visitor count on my resume, utilizing the call to my API. To do that, I also had to set up an API gateway to my lambda function. After this, I wrote some tests in Python to make sure my API was working properly. I wrote unit tests, integration tests, and end-to-end tests. I had some experience in Selenium, so this time, I chose to try out puppeteer, doing something new.

To my surprise the code was closer in structure to the puppeteer version than it was to the chromedp. The chromedp version uses nested context declarations to manage the browser and page runtimes, the rust version uses a more linear approach. You construct a browser instance and then you can interact with it as a user would. This points at the fact that the chromiumoxide api is higher level.

In this tutorial, we can extract data from the HTML structure, so we will go with Cheerio, but for extracting data from SPAs or JavaScript-rendered websites, Crawlee also supports headless browser libraries like Playwright and Puppeteer