Victor Gladkikh

I can confirm this issue when using chrome node in docker or k8s Tried: `selenium/node-chrome:4.5` and `selenium/node-chrome:4.6` Tried exact version from documentation. One note: standalone-chrome docker is working fine. It's...

@dimsamaras I have tried to follow doc steps with [hubs and nodes](https://playwright.dev/docs/selenium-grid#hub-and-nodes-mode). It just don't work. Any suggestion on how to debug this issue deeply to investigate what can go...

Okay, my bad. Take some time and completed run for different Selenium Grid version: - 4.3 works fine - 4.4 works fine - 4.5, 4.6 are failing with logs below...

Attaching `pw*` log against 4.6 Selenium Grid [debug.log](https://github.com/microsoft/playwright/files/10064706/debug.log)

Just to keep up to date Same issue is in Selenium Grid v4.7.1

`Bower` officially propose to use `yarn` or `webpack` as a replacement for `bower` - https://github.com/bower/bower/issues/2298 There is even an old blog post from `npmjs` team - http://blog.npmjs.org/post/101775448305/npm-and-front-end-packaging