Open aaronjensen opened 7 years ago
Yarn v0.17.2
still broken on it. NPM installs package phantomjs-prebuilt
correctly.
OS X Sierra
Node.js v7.1.0
phantomjs-prebuit v2.1.13
yarn unlike npm does not install phantomjs binary only script relying on it. As a workaround I downloaded phantomjs binary a set PHANTOMJS_BIN env variable pointing to it.
Another fix for this is to run rm -rf node_modules/
and re-run yarn
. I'll see if I can investigate this issue a little further.
Thanks, @RSO. Worked for me. (Still broken as of yarn 0.18.1)
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Yarn appears to occasionally corrupt the native portion of phantomjs-prebuild, especially when used within docker.
This manifests like this:
If the current behavior is a bug, please provide the steps to reproduce.
Our repro is fairly complicated and involves blowing way the yarn cache (though it still seems to happen for us even without the yarn cache being taken away).
See this repo for repro steps: https://github.com/aaronjensen/yarn-repro
Some notes about this repo:
.yarn-integrity
is meant to simulate theyarn.lock
changing in any way. We typically see this behavior when theyarn.lock
changes.--cache-folder .yarn-cache
to bothyarn
commands, but in our real world scenario this does not seem to consistently help.What is the expected behavior?
Yarn would not corrupt phantomjs's binary ever, even if the yarn-cache was gone.
Please mention your node.js, yarn and operating system version.
Node 6.5.0 yarn 0.16.1 Debian 8 (jessie)