So, here’s what I guessed I had to do, and I just went ahead and tried it. (Remember, I have -zero- experience with node or electron or javascript, so you’re dealing with a fearless 2-year old here - "cross the busy road - sure!)
I had no idea where such code might go, so I did a find through the project:
find . -name electron-chromedriver* -ls
(which found nothing)
I thought to grep for this module, and did find it:
grep -ir electron-chromedriver
node_modules/electron-download/package.json: “/electron-chromedriver”
node_modules/extract-zip/package.json: “/electron-chromedriver”
npm-shrinkwrap.json: “electron-chromedriver”: {
npm-shrinkwrap.json: “resolved”: “https://registry.npmjs.org/electron-chromedriver/-/electron-chromedriver-3.0.0.tgz”,
npm-shrinkwrap.json: “electron-chromedriver”: “~3.0.0”,
That pointed me to node-modules as the place where node modules go (obvious in retrospect), and gave me a clue of where to download it from. So I downloaded that URL, created a new directory under node-modules called “electron-chromedriver” and unpacked it there.
I read the README.md file and found a line that looked like it should install the module, so I tried it:
npm install --save-dev electron-chromedriver
> electron-chromedriver@7.0.0 install /home/pi/Documents/etcher/node_modules/electron-chromedriver
> node ./download-chromedriver.js
> undefined postshrinkwrap /home/pi/Documents/etcher
> node ./scripts/clean-shrinkwrap.js
[OK] Wrote shrinkwrap file to ../npm-shrinkwrap.json
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: winusb-driver-generator@1.2.4 (node_modules/winusb-driver-generator):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for winusb-driver-generator@1.2.4: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
+ electron-chromedriver@7.0.0
added 1 package from 1 contributor, updated 1 package and audited 13389 packages in 64.918s
found 321 vulnerabilities (1 low, 10 moderate, 310 high)
run `npm audit fix` to fix them, or `npm audit` for details
So, there’s a lot of slightly worrying output there. Should I be concerned?
The README suggested doing “chromedriver -h”, which I tried but it couldn’t find such an executable. I rooted around and found it within the apparently-newly-created bin directory within the module, which makes me think the install succeeded, and in fact it does execute and I got the expected help.
I will proceed to try the “make electron-develop” again.