Please refer to the below article written by one of our Team members. We have seen similar issues with puppeteer not working with Function Windows platform. For Function app on windows, it might be hitting the sandbox limitation.
I like to tweet about code and post helpful code snippets. Dec 28, 2022, 4:19 AM Puppeteer is node.js library to control chromium and it would work with Linux platforms. The final step is close your terminal, and reopen it and run your NPM or Yarn installs. zshrc file and add the following 2 lines of code:Įxport PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=trueĮxport PUPPETEER_EXECUTABLE_PATH=`which chromium` Go to your System Preferences > Security & Privacy > General screen, and select Open Anyway. Open Chromium on your machine, and you may receive an alert message as such: If your M1 Mac doesn’t allow third party apps to be open, you may need to give Chromium permission to do so. Step 2: Allow Chromium to open on your M1 Mac The chromium should in the homebrew binary directory, as such: If you want to check which chromium your M1 Mac is using, type the following command: Once you do, open up the terminal and type the following command: Make sure you have Homebrew install on your M1 Mac. Let’s go over how to fix this problem step-by-step. The answer is to manually install chromium on your machine.
Path-to-project/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:112 If you are on Ubuntu, you can install with: The chromium binary is not available for arm64: I recently got the M1 Mac mini computer, and ran yarn or npm to install a project that contained Puppeteer in the package.json file, and I received this error message:
0 kommentar(er)
