2 years ago
They now always stop and time out at the same step - which is the stage shown in the screenshot. The same code was working and deploying alright last week. I just commented out an irrelevant function that unrelated to anything that's got to do deployments.
10 Replies
2 years ago
installing puppeteer (aka installing chrome) is known to be buggy, instead I would recommend using browserless so you can skip installing chrome altogether, it's also going to result in smaller and therefore faster build, publish, and deploy times, we have a browserless template here -
and an example repo here, with extra information -
but it worked for the whole past year, i cant transition now to a different implementation
my business is already running here, I'm using puppeteer to create personalised images that get printed
2 years ago
it would be incredibly easy to adopt browserless, please check out the example repo
I love you Brody, but this isn't the type of solution im looking for in this situation, i did a minor update to an already working project. I wouldn't expect it to just stop working all of a sudden
2 years ago
I understand it may not be the solution you are looking for, but as I mentioned installing puppeteer (chrome) is known to be buggy, so it's best to simply avoid it, and you can avoid it by using browserless.
either way, I don't have any other solutions.
I appreciate your help, you helped me set the project up in the first place. This project was already very stable and I don't want to touch it too much anymore. Just a bummer I can't make minor tweaks all of a sudden. I remember browserless not working for my use case when I was first setting the project up, but I don't remember what my issue with it was.
Anyways, hoping someone else can chime in!
2 years ago
the last shot in the dark I'd try would be to write a Dockerfile
2 years ago
@Panda if you need help with puppeteer and browserless (basically lets you not have to deal with installing chrome at all) dm me. I just worked through this last week