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
ENOENT yarn when yarn not present inside bold/node_modules/.bin since there are conditions like inside Runners where .bin path is not linked properly.
Detailed description
This issue present when we use Codeship Build process. Codeship environment has different way of linking, mapping, caching installed packages so it is not a good option to think that we will have yarn installed and linked for us. This pull request introduces simple fix using npx command.
Type of change
Non Breaking change
Checklist:
Replace relative path of yarn with npx command
Put yarn command inside first argument of execution inside child process
Fix Tests to fit new flow when using yarn with npx
Expected arguments inside yarn.test.js are now 2 instead of 1
Removed project-bin-path from dependencies since npx is more powerful
yarn
installed and linked for us. This pull request introduces simple fix usingnpx
command.Type of change
Checklist:
yarn
withnpx
commandyarn
command inside first argument of execution inside child processyarn
withnpx
yarn.test.js
are now 2 instead of 1project-bin-path
from dependencies sincenpx
is more powerful/home/rof/.nvm/versions/node/v10.16.0/bin/yarnpkg -> /home/rof/.nvm/versions/node/v10.16.0/lib/node_modules/yarn/bin/yarn.js /home/rof/.nvm/versions/node/v10.16.0/lib └── yarn@1.19.0 ⚡️ bolt v0.24.2 (node v10.16.0) 🔎 [1/4] Validating project... 📦 [2/4] Installing project dependencies... error Error: spawn /home/rof/src/github.com/camplight/consento/node_modules/bolt/node_modules/.bin/yarn ENOENT
The text was updated successfully, but these errors were encountered: