Webdriver.io中Selenium Standalone启动报错：缺失Chrome依赖

Hey there! Let's tackle this chromedriver missing error you're hitting with selenium-standalone 6.18.0. I've seen this pop up a few times, usually tied to incomplete downloads or version mismatches. Here are some step-by-step fixes to try:

1. Clean and Reinstall Selenium Dependencies #

The most common fix is to clear any partial or corrupted driver downloads and start fresh. Run this command in your project directory:

./node_modules/.bin/selenium-standalone install --clean

This will wipe the existing cache in node_modules/selenium-standalone/.selenium/ and re-download all required drivers (including the missing chromedriver version 83.0.4103.39-x64).

2. Verify Chrome Browser and Chromedriver Version Match #

Chromedriver must match the major version of your installed Chrome browser. The error shows it's looking for chromedriver 83.0.4103.39, so:

• Check your Chrome version (go to chrome://settings/help to see it)
• If your Chrome is a different major version (e.g., 114.x), you'll need to force selenium-standalone to install the matching chromedriver. Replace <your-chrome-version> with your actual Chrome version number and run:

./node_modules/.bin/selenium-standalone install --drivers.chrome.version=<your-chrome-version>

3. Manually Download and Place Chromedriver #

If the automatic download fails (often due to network restrictions), you can manually add the driver:

• Locate the 64-bit chromedriver version 83.0.4103.39 (match the version in your error)
• Download and extract the executable
• Rename the file to 83.0.4103.39-x64-chromedriver (exactly as shown in the error path)
• Move it to the directory: C:\Projects\WebdriverioFramework\node_modules\selenium-standalone\.selenium\chromedriver\

4. Try Running the Command in a Different Shell #

If you're using MINGW64, sometimes path resolution can be finicky. Try running the start command in a regular Windows Command Prompt (CMD) instead:

node node_modules/.bin/selenium-standalone start

After trying any of these steps, re-run your original start command and see if the error clears up.

内容的提问来源于stack exchange，提问作者Hemant Varhekar