You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to request a feature or report a bug?
bug
What is the current behavior?
The packages geckodriver and chromedriver in their current respective versions (1.16.2, 76.0.0) cannot be yarn added at the same time. If they are in the same package.json and being installed at the same time, yarn install fails.
If the current behavior is a bug, please provide the steps to reproduce. yarn init yarn add geckodriver chromedriver
Output:
yarn add v1.17.3
warning ../../../package.json: No license field
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/2] ⠄ geckodriver
error /home/aleks/var/tmp/geckodriver-test/node_modules/geckodriver: Command failed.
Exit code: 1
Command: node index.js
Arguments:
Directory: /home/aleks/var/tmp/geckodriver-test/node_modules/geckodriver
Note, this was attempted by several co-workers, and not everybody could reproduce it on their machine. We have the same OS (Ubuntu 19.4) but different machines. My CPU (on which it fails) is:
Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
A coworker who could reproduce the problem had the same machine & CPU. It may be a hardware problem.
Also, non-parallel installation, by yarn adding the packages individually was no problem, and can be used as a workaround (but yarn install if both are in the same package.json is still broken.)
npm install --save geckodriver chromedriver with both packages at the same time works.
Some additional information: The command does work in docker, using the official node image, on my machine & Ubuntu installation.
I've also attached the output of yarn's --verbose option for the above command. yarn.log
I've also tried it with Ubuntu's own yarnpkg version of 1.13.0. It worked fine with that yarn version, so downgrading is also a possibility. I've no idea when the regression was introduced.
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
bug
What is the current behavior?
The packages
geckodriver
andchromedriver
in their current respective versions (1.16.2, 76.0.0) cannot beyarn add
ed at the same time. If they are in the samepackage.json
and being installed at the same time,yarn install
fails.If the current behavior is a bug, please provide the steps to reproduce.
yarn init
yarn add geckodriver chromedriver
Output:
Note, this was attempted by several co-workers, and not everybody could reproduce it on their machine. We have the same OS (Ubuntu 19.4) but different machines. My CPU (on which it fails) is:
A coworker who could reproduce the problem had the same machine & CPU. It may be a hardware problem.
Also, non-parallel installation, by
yarn add
ing the packages individually was no problem, and can be used as a workaround (butyarn install
if both are in the samepackage.json
is still broken.)npm install --save geckodriver chromedriver
with both packages at the same time works.The offending
package.json
:If I should provide more info/assistance, please let me know.
What is the expected behavior?
Installation should not be a problem.
Please mention your node.js, yarn and operating system version.
Some additional information: The command does work in docker, using the official
node
image, on my machine & Ubuntu installation.I've also attached the output of yarn's
--verbose
option for the above command.yarn.log
I've also tried it with Ubuntu's own
yarnpkg
version of 1.13.0. It worked fine with that yarn version, so downgrading is also a possibility. I've no idea when the regression was introduced.The text was updated successfully, but these errors were encountered: