Hi, On 2022-01-04 19:10, Martina Ferrari wrote: > On 03/01/2022 08:13, Andrius Merkys wrote: > >> I have revisited puppeteer packaging. I have collected missing >> dependencies, packaged a missing one, node-devtools-protocol, and >> attempted to update to the newest upstream release. However, both old >> and new puppeteer versions FTBFS with tsc failures, most likely rising >> from incompatibilities of node packages. >> >> The least problematic seems the failure of puppeteer/13.0.1 with >> devtools-protocol/0.0.953906: >> >> src/common/Coverage.ts(277,7): error TS2558: Expected 1 type arguments, >> but got 4. >> src/common/Page.ts(1798,38): error TS2558: Expected 1 type arguments, >> but got 2. >> >> However, I have no idea about how to fix or debug that. I have pushed >> packagings of newer package versions to salsa, to package-v* branches, >> should you wish to give them a look. > > Thanks for the update! > I will take a look. Do you prefer that I send you merge requests or to > commit directly?
Please feel free to commit directly. >> Another blocker is chromium, which is currently not installable (see [1] >> for reference). Firefox-based backend for puppeteer is also available, >> albeit deprecated. I have not tried it yet, though. > > > I am not too worried about chromium being uninstallable, surely > *somebody* will fix that! Firefox support seems to still be > experimental, and in any case, the puppeteer package will not care no? I am not sure, though. Puppeteer is prepared to download browsers by itself, but puppeteer-core would rely on system/user-installed browsers. I am particularly interested in the latter case as some packages use puppeteer to execute test suites. Best, Andrius
