We're finally going to be able to spot when someone is using PercyScript (rather than it always showing as the Puppeteer SDK).
This does duplicate most of the puppeteer SDK, but that's okay. Every other SDK uses the same exact pattern for extracting the DOM from the test browser and then POST'ing that back to the agent process. I don't think we're actually DRYing anything up.
RE: fix vs. feat, I'd consider this a bug if it didn't report properly. So probably fix even though we're changing deps and internal logic, the public API stays the same with the addition of the client info.
What is this?
We're finally going to be able to spot when someone is using PercyScript (rather than it always showing as the Puppeteer SDK).
This does duplicate most of the puppeteer SDK, but that's okay. Every other SDK uses the same exact pattern for extracting the DOM from the test browser and then
POST
'ing that back to the agent process. I don't think we're actually DRYing anything up.TODO:
fix:
vsfeat: