Puppeteer 不会打开 chrome（出现错误）

Question

I am running an elastic-beanstalk instance on AWS and am trying to build a pdf export functionality on a dashboard using Puppeteer. I got the application to work locally, however when i run the export feature on the cloud i get the following error.

(node:1434) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome! /var/app/current/node_modules/puppeteer/.local-chromium/linux-674921/chrome-linux/chrome: error while loading shared libraries: libXcursor.so.1: cannot open shared object file: No such file or directory

To deploy i am zipping the contents of the application (without the node modules fails upload if included) and deploying on the following configuration:

Environment tier:
Web Server

Platform:
Node.js running on 64bit Amazon Linux/4.10.1

Health status:
Ok

I had struggled to get the application to deploy until i included a .npmrc file. However now i am having trouble running the functionality.

Answer 1

看起来您缺少一些 Debian 依赖项，希望此链接有帮助。

Answer 2

GitHub repository maintained @ https://github.com/amarinediary/Marionette . The following might not be up to date. Refer to the GitHub link for a maintained version.

---

You can add AWS Elastic Beanstalk configuration files ( .ebextensions ) to your web application's source code to configure your environment and customize the AWS resources that it contains.

In our case, if we don't enable EPEL and if we continue installing Chromium as part of npm install, Puppeteer cannot launch Chromium due to unavailability of libatk-1.0.so.0 .

• Source @ Running Puppeteer on AWS EC2 instance running Amazon-Linux

Hotfix

Add the following to your app root:

1. Create a .npmrc file.
2. Add the following to your .npmrc file:

unsafe-perm=true

The .npmrc file defines how npm should behave when running commands. Setting unsafe-perm to true suppress the UID/GID switching when running package scripts. Set the unsafe-perm flag to run scripts with root privileges.

• Source @ unsafe-perm

3. Create a .ebextensions folder.
4. Inside .ebextensions folder, create a 01_enableEPEL.config file and add the following.

commands:
  01_enableEPEL:
    command: sudo amazon-linux-extras install epel -y

5. Inside .ebextensions folder, create a 02_installEPELPackages.config file and add the following

packages:
  yum:
    chromium: []