[🐛 Bug]: SeleniumServer does not start selenium 4.x jar standalone

What happened?

Selenium server can not start selenium 4.4.0 as a standalone server

How can we reproduce the issue?

const { SeleniumServer } = require('selenium-webdriver/remote');

test();
async function test() {
  const pathToJar3xJar = './.selenium/selenium-server/3.141.59/selenium-server.jar';
  const pathToJar4xJar = './.selenium/selenium-server/4.4.0/selenium-server.jar';

  const args = {
    args: [],
    jvmArgs: ['-Dwebdriver.chrome.driver=./.selenium/chromedriver/latest-x64/chromedriver'],
    port: undefined,
  };

  // this works fine
  const server3xJar = new SeleniumServer(pathToJar3xJar, args);
  /* does not work
  the problem that selenium 4.х requires "standalone" right after the jar file what is not happen
  when the same args are used
  */
  const server4xJar = new SeleniumServer(pathToJar4xJar, args);
}

Relevant log output

Error: Server terminated early with status 0
      at /node_modules/selenium-webdriver/remote/index.js:249:24

Operating System

macOS Ventura

Selenium version

4.7.0

What are the browser(s) and version(s) where you see this issue?

What are the browser driver(s) and version(s) where you see this issue?

Are you using Selenium Grid?

No response

[potapovDim]

@harsha509 https://github.com/SeleniumHQ/selenium/pull/11412

[harsha509]

Hi @potapovDim ,

Sure, if you’ve fix ready, could you please raise the PR.

I have time today will take a look!