It will ask you some questions, I went with the default for everything, except that I named my entry point file for "pdf.js" instead of "index.js" npm initĤ. Ignore the folder that will contain puppeteer and any other node module: echo '/node_modules' >.
I changed a few commands and skipped a couple, so here's what I did:ġ. cd into the folder containing your Rails project.Ģ. To get node running alongside Rails, this great article helped me on the right track: just that it can be done and had no negative impact on my experimental project Adding node modules to your Rails appįirstly, make sure you have npm and node installed and with a recent version (I'm using 8.6.x): and it's maintained by Google themselves. Resulting PDF's from my experiments so far look perfect!ĭISCLAIMER: I'm not saying the below is a good idea, or even that I know what I am doing. This means it handles HTML5, CSS3 and Google fonts, which the other alternatives have always had troubles with. This is the same idea behind wkhtmltopdf and PhantomJs but puppeteer is powered by a modern and maintained browser. Headless is great because it means we can use much of the same functionality of a normal Chrome browser, but can be run entirely on a remote server. However, running a node.js library from within a Rails app was not something I'd done before and I couldn't find a lot of info or complete instructions, so I decided to document it here for my own future reference.
0 kommentar(er)
