Matchu
9ec917e4d3
So, just using normal playwright was crashing with this error: https://github.com/microsoft/playwright/issues/5862 I didn't understand why everyone was using playwright-core until I read the comments more carefully, and saw that it was because folks were using playwright-aws-lambda, because that's where Vercel functions run. (It has some special compat stuff.) So I'm figuring that maybe the special case in Vercel's builder that fixes this for playwright-core maybe doesn't apply to normal playwright? But that people don't actually run into that issue in practice, because they're all using playwright-core for playwright-aws-lambda instead? Idk, let's see how it goes! My hope is that this both fixes the immediate crasher about browsers.json being missing, _and_ fixes a problem we were _gonna_ have down the line about normal playwright not working in an AWS Lambda setting. |
||
---|---|---|
.. | ||
allWakaValues.js | ||
assetImage.js | ||
graphql.js | ||
outfitImage.js | ||
outfitPageSSR.js | ||
sendFeedback.js | ||
uploadLayerImage.js | ||
validPetPoses.js |