Microsoft has released Playwright, a Node-based browser automation library that drives headless browser instances: navigate, click, capture screenshots, and similar operations. Its primary use case is automated testing.
The closest point of comparison is Google's Puppeteer. The difference Playwright claims is reach: where Puppeteer is Chrome-only, Playwright also "works" in Firefox and Safari.
The compatibility question
That claim drew immediate pushback. In the replies to the launch tweet from Andrey Lushnikov — whose bio reads "former TL @ Chrome Puppeteer, former eng @ Chrome DevTools" — Sam Sneddon questioned how genuine the cross-browser support is.
Per Maciej Stachowiak, the compatibility rests on very large patches to the browsers in question. Critics describe the arrangement as a house of cards unlikely to ever land upstream, particularly given competing efforts such as puppeteer-firefox.
Where the code came from
The lineage is not subtle: the original Google team behind Puppeteer effectively moved to Microsoft and redid the work there. The report notes Google is none too pleased about it.
The open-source strategy angle is what complicates Microsoft's position. A company that has done well by open source hiring away a team to build a directly competing open-source project — one that integrates with other open-source projects without much cooperation from them — is not a great look. The counterweight is obvious enough: a working project that gives you cross-browser headless control is genuinely useful.
Elsewhere in the space
Cypress, as understood here, uses neither Playwright nor Puppeteer but its own implementation. It is close to Firefox support as well.
The Playwright source lives at github.com/microsoft/playwright.



