-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example not working when I publish #40
Comments
Your browser is starting properly, but must likely puppeteer isn't working. Just use the 1.0.3 puppeteer with the 67 binary and you'll be good to go. Also, change the package.json |
@vbrundic
Both resulted in the same error. Please help
|
I was running into this same issue and it was due to a newer version of puppeteer being installed. I deleted my node_modules folder then pinned the version of puppteer in my package.json to |
It would be nice if anyone states explicitly the versions which are compatible with this lib :) |
I had "puppeteer": "1.1.1" and it was silently failing, without any exceptions. |
With this version I can't find a puppeteer version that works, not even 1.1.0 :( It gets stuck in this line |
@feliun I am using the other file |
I just downloaded the exact example from the repo, deployed the lambda and didn't work out of the box with 1.1.1. Some people stated the puppeteer version should be downgraded but not even like that. If it's not the code, could it be something different on my lambdas @jprivillaso ? Maybe the region or the stage? |
Bloody hell! Yeah I was using the caret coming from the repo. When I changed my package.json to |
I can share later the codebase that I am using if you want |
I had the same problem. I've submitted two PRs to update this starter kit: Hopefully these PRs will be integrated soon. Otherwise, you can find them already integrated on my fork: https://github.com/mglasgow/puppeteer-lambda-starter-kit |
Hi everyone,
I can't make it run the basic sample at index script on a lambda function, here's what I did:
Clone this repo and then run npm install... test locally and works.
Then I run serverless deploy, everything get published, but when I run I always have this issue:
"errorMessage": "No node found for selector: #lst-ib", (to test, I simply go to the lambda function, and run a test)
Actually, I can't inspect any element, If I use waitForSelector I have a timeout, so I assume that page never get loaded.
Here's part of log:
Is there an issue with this build or I'm missing something?
Thanks in advance.
The text was updated successfully, but these errors were encountered: