JavaScript as a server-side technology sucks. It was cool back in 2010 when NodeJS first came out and event loops were all the rage. But .NET is now 10x faster than NodeJS, statically typed, has better community support, better tooling, broader official libraries, better package manager, and as a bonus it's not JavaScript. The productivity and performance of .NET with Visual Studio is just unmatched.
Also regardless of keeping it in a _single_ language or tool, one might prefer to write tests in a .net language instead of js or python.
But yes, spending my weekends learning a new language and library is not a feature.
I'd much prefer to spend my off time learning more about my target users, how to better manage a team, or the legal regulations surrounding the domain I'm writing code in, or just hitting the gym...
Not to mention as soon as I add a new language to our project stack that means every current dev has to learn a new technology, our build pipeline becomes more complex, we need a second set of coding guidelines, and finding new devs becomes more difficult because they'll need to know 2 languages instead of one or we have to increase the onboarding time for every future dev who roles onto the project.
I think it's uncommon that it's worthwhile to invest in a second language/tech stack on a real project.
Personally, I work with both C# and JavaScript, and I'd happily use the C# version of Playwright to write and run UI tests.
Why do You think that this will somehow limit people ability to learn or even make them worse version of them?
Most of the dev's I know, want to do coding for life: - not learning tools from scratch every few weeks, because of the abandoned library - not fight with npm audit every week - not waiting for 5 minutes for webpack to download internet and build project in CI, while .Net builds are already completed, unit tested and waiting for smoke run.
What's the alternative? Prepare the backend via exclusive frontend operations? That has its own issues like possibly being impossible (e.g. maybe making an admin isn't exposed to the webapp) or being slow, or not being able to create data in a "legacy" state that the current frontend can't do.
Or maybe use C# to create and teardown the data, but then call out to a nodejs process in the middle of the test?
I am legitimately curious how you would test a C# app exclusively from nodejs.