As promised last month, We shipped PlaywrightSharp.Firefox v0.10! You can read more about this version on my previous post.

Playwright-Sharp as a Playwright client?

We are working with the Playwright team on a Playwright RPC Server.


This Playwright server would package a (Node.JS) playwright instance, exposing its functionality through pipes. Remember I talked about pipes?

If we land with this idea (this is still a proof of concept), we will be able to speed up Playwright-Sharp development, allowing us to work on many other things I have dreamed for this library. I want Playwright-Sharp to be not only a cool library, but the best automation suite for .NET developers.

I’m sharing with you this internals because that’s the purpose of these reports. But Playwright-Sharp wouldn’t feel like just a client. It will be a first-class citizen, and you will be able to use it in the same way you’d use playwright.

So maybe, and this a huge maybe, we would be able to ship a V1 in the next 40 days.


  • Repository Stars: 117 (prev 94) +24%
  • Repository Forks: 8 (prev 7) +14%
  • Nuget downloads: 274
  • Contributors: 1


  • Meir Blachman is doing most of the job on the Firefox project, so if you get to use Playwright-Sharp with Firefox, thanks Meir!

Final words

Now that we shipped our first versions, I’m looking forward to getting more feedback. The issues tab in GitHub is open for all of you to share your ideas and thoughts.
Don’t forget to follow me on Twitter @hardkoded to get more updates.

Don’t stop coding!

Previous Reports