Skip to content

Releases: jontewks/puppeteer-heroku-buildpack

Heroku-24 Support

05 Aug 17:46
a2332f4
Compare
Choose a tag to compare
Heroku 24 support (#137)

* Heroku 24 support

* Update with specific new package for heroku 24

Heroku-18 specific buildpack

19 Oct 17:44
Compare
Choose a tag to compare

Adds packages that aren't available at runtime in heroku-18

Heroku-22 without xdg-utils library

09 Aug 18:28
Compare
Choose a tag to compare

The largest library required by Puppeteer is xdg-utils, but I couldn't find what specifically it was used for. I tested without this library and the very basic app still loads and runs successfully on Heroku, but I'm assuming there is going to be some functionality that fails due to this missing package. If you are in dire need of a smaller slug size, you might be able to use this version if whatever you are doing doesn't require xdg-utils.

Good luck.

Reset package list to current Puppeteer requirements

09 Aug 17:44
Compare
Choose a tag to compare

Reset the list to only the packages required for running puppeteer on Heroku-22 and starting to keep the major version number of the buildpack tied to the Heroku stack it represents.

List of common Puppeteer missing requirements here: https://pptr.dev/troubleshooting
List of packages available on Heroku stacks: https://devcenter.heroku.com/articles/stack-packages#installed-ubuntu-packages

This tag only includes the things in the first list not in the second list.

Add package for puppeteer v3

18 Apr 21:36
Compare
Choose a tag to compare

Adds a single package to support puppeteer v3.0.0

Write to unique location and stop logs about deprecated force-yes flag

15 Oct 17:32
Compare
Choose a tag to compare
Don't use deprecated `apt-get --force-yes` (#30) (#31)

I noticed in my heroku build log that there's a bunch of `apt-get` warnings like this:

```
W: --force-yes is deprecated, use one of the options starting with --allow instead.
```

It looks like this line is the one responsible: https://github.com/jontewks/puppeteer-heroku-buildpack/blob/22c5b5960775a5befb89e8b9a1014bc8c1187e3f/bin/compile#L56

According to the [`apt-get` man page](https://manpages.debian.org/stretch/apt/apt-get.8.en.html),
we can use `--allow-downgrades --allow-remove-essential --allow-change-held-packages` instead.

Fixes https://github.com/jontewks/puppeteer-heroku-buildpack/issues/29

Add even more dependencies that went from run to build time on heroku-18

16 Sep 20:52
Compare
Choose a tag to compare
1.1.5

Add more 16 -> 18 stack dependencies that went from run to build time…

Account for stack changes to build vs run time on heroku-18

16 Sep 20:51
Compare
Choose a tag to compare

Two packages were causing some users issues and I found out that on the heroku-16 stack those packages were available during run time, but on the heroku-18 stack they changed it so those packages were only available during build time. This change adds those packages as named dependencies.

https://devcenter.heroku.com/articles/stack-packages

Add unlisted puppeteer dependencies

13 Sep 16:19
Compare
Choose a tag to compare

Adds back some removed dependencies that aren't listed as required for Puppeteer / chromium

Match newest Puppeteer dependencies list

10 Sep 16:41
c2b91bf
Compare
Choose a tag to compare