Update puppeteer from v1.11.0 to v2.1.1 (latest)

[chrisklus]

This update will fix phetsims/chipper#928.

I'm not sure who to ask before doing this and what all needs to be checked after it's updated. If updating to the latest version is problematic, a small update to v1.12.0 will likely still fix the above issue.

Assigning to @zepumph and @samreid for now, please feel free to unassign and recommend someone else.

[zepumph]

I don't think perennials puppeteer is used for update phet io files. Wouldn't it be chippers? I updated chippers to fix an npm vulnerability last month.

…

On Sat, Apr 4, 2020, 14:53 Chris Klusendorf ***@***.***> wrote: Assigned #170 <#170> to @zepumph <https://github.com/zepumph>. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#170 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUKB33QCYYTNG6XZCBD6LLRK627XANCNFSM4L7LNWLQ> .

[samreid]

Why does perennial even have puppeteer? It was added in #138 by @zepumph, so I'll leave assigned to him for discussion.

Yes, chipper's puppeteer updates the phet-io files.

[chrisklus]

Oh whoops, yeah the problem from phetsims/chipper#928 is fixed if i revert my local update in perennial and npm prune && npm install in chipper. Thanks.

[zepumph]

Why does perennial even have puppeteer?

I added it for the PDOMComparison task.

I think this issue is now a duplicate of phetsims/chipper#949. Closing