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
[x] Non Breaking change
Checklist:
[x] Replace relative path of yarn with npx command
[x] Put yarn command inside first argument of execution inside child process
[x] Fix Tests to fit new flow when using yarn with npx
[x] Expected arguments inside yarn.test.js are now 2 instead of 1
[x] Removed project-bin-path from dependencies since npx is more powerful
Stradivario
commented
5 years ago
Issue
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
Checklist:
yarnwithnpxcommandyarncommand inside first argument of execution inside child processyarnwithnpxyarn.test.jsare now 2 instead of 1project-bin-pathfrom dependencies sincenpxis more powerful