When using yarn with the nodejs plugin, the yarn binary is not in $PATH

Bug #1685551 reported by Leo Arias on 2017-04-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Medium
Sergio Schvezov

Bug Description

I was trying to build a snap for ethereum's mist. It uses yarn as the package manager, but it has an entry in package.json that we don't support:

"postinstall": "cd interface && yarn"

https://github.com/ethereum/mist/blob/develop/package.json#L11

Trying to build this snap will fail with:

error /home/elopio/mist/parts/mist/src/node_modules/Mist: Command failed.
Exit code: 127
Command: sh
Arguments: -c cd interface && yarn
Directory: /home/elopio/mist/parts/mist/src/node_modules/Mist
Output:
sh: 1: yarn: not found

In order to support this use case, during the pull and build, the commands need to be able to execute parts/<name>/bin/yarn.

Sergio Schvezov (sergiusens) wrote :

It was like that on purpose, it was clearly a mistake.

Changed in snapcraft:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Sergio Schvezov (sergiusens)
milestone: none → 2.35
Changed in snapcraft:
milestone: 2.35 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers