Skip to content

bug(Yarn): replaced relative path to bin with npx and first argument #253

@Stradivario

Description

@Stradivario
Title Description
Version 0.24.2
Type Issue
node 10.16.0
Operating System Ubuntu 18.04 LTS
Short Description 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
/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
└── [email protected] 

⚡️   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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions