Next, using the puppeteer package we imported up top, we create an instance of a web browser with puppeteer.launch(). Below that import, we create a skeleton for our generatePDF() function, taking in a single argument html as a string.Ĭonst browser = await puppeteer.launch() This is what we'll use to generate our PDF. Here, we begin by importing the puppeteer dependency we installed earlier. lib/generatePDF.js import puppeteer from "puppeteer" This function will take in some HTML and CSS for the contents of our PDF and then output it as an actual PDF: Our first task is to write the function that we'll use to actually generate our PDF. Next, install the dependencies for the boilerplate:Īfter that, we need to install the puppeteer package from NPM which will help us generate our PDF:įinally, start the development server up:Īfter this, we have everything we need to do our work.
First, let's clone a copy of that to our computer: puppeteerrc.cjs (or this tutorial, we're going to use the CheatCode Node.js Boilerplate to give us a starting point for our work. Puppeteer uses several defaults that can be customized through configurationįor example, to change the default cache directory Puppeteer uses to installīrowsers, you can add a. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Your project folder (see an example below) because not all hosting providers Heroku, you might need to reconfigure the location of the cache to be within If you deploy a project using Puppeteer to a hosting provider, such as Render or
The browser is downloaded to the $HOME/.cache/puppeteer folderīy default (starting with Puppeteer v19.0.0). When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to
0 kommentar(er)
