Chrome is launched instead of phantomjs in 6.13.0

[Emilez]

Expected Behavior

PhantomJS can be started without problems.

When I try to start phantomjs I get an error message related to Chrome "loading of unpacked extensions is disabled by the administrator".

Current Behavior

When I try to start phantomjs I get an error message related to Chrome "loading of unpacked extensions is disabled by the administrator" and the chrome browser is launched instead.

The same issue is describer here although he uses wdio and I use the stand-alone version of webdriverio.
#349
but I think the root cause is selenium-standalone as the writer in the linked issue points out.

Steps to Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include commands that you used
in the shell, or snippets of how you are using the JavaScript API.

1. Start a selenium test with phantomjs browser and webdriverio stand-alone version.

Logs

desired configsent to webdriverio:
{ browserName: 'phantomjs',
'phantomjs.binary.path': 'C:\Utveckling\gitProd\mig-selenium-trunc\node_modules\phantomjs-prebuilt\lib\phantom\bin\phantomjs.exe' }

Your Environment

• Version of selenium-standalone that you are using: 6.13.0
• Is there another tool calling selenium-standalone on your behalf: webdriverio standalone
• System/platform: Windows 10
• Other details that might be important:
  "webdriverio": "4.12.0",
  "phantomjs-prebuilt": "2.1.16"

[Emilez]

I verified that it is between version 6.12.0 and 6.13.0 that this issue is introduced. Probably a selenium-standalone issue but could also be an integration issue between something else and selenium-standalone I guess. But probably selenium-standalone.

[Emilez]

Okay, selenium does not aupport phantomjs anymore as of 3.8.1
SeleniumHQ/selenium#5295

However there seems to be a workaround for those who know how to do it.

"
Given that the PhantomJS driver in Java was a third-party jar that was packaged in the standalone server as a convenience, you should be able to include the same jar as a dependency in your own project and get that functionality back. Moreover, since the Java PhantomJS driver was not maintained by the Selenium project, I’m not entirely sure how it could’ve been marked as deprecated before removal. Finally, this would only apply to the Java bindings, since the phantomJS driver in the other language bindings is part of the Selenium project.Disclaimer: This isn’t an “official” project position. You asked for my take, so I’m giving it. Now I’m going back to my holiday.

"