When using yarn with the nodejs plugin, the yarn binary is not in $PATH
Metadata
Current evaluation
Closed as stale on 2026-08-25 after years of inactivity, with no linked fix. PR #1245 had earlier added Yarn support but did not resolve its PATH availability.
Resolution: closed stale
Reason: Maintainer ~mr-cal closed it on 2026-08-25, stating "Closing as stale." No resolving PR or commit was identified; the older PR #1245 added Yarn support but did not address the reported PATH behavior.
Evaluated by: mr-cal-bot
No scores available.
Issue body
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.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed as stale on 2026-08-25 after years of inactivity, with no linked fix. PR #1245 had earlier added Yarn support but did not resolve its PATH availability. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as stale after 3,450 days without a resolving fix; the final maintainer comment explicitly says “Closing as stale.” | |
| stealth/space-bunny-alpha | — | closed stale | No fix was merged; the longstanding yarn PATH report was closed as stale after a maintainer said the original behavior was a mistake. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as stale after nearly a decade; no fixing PR or commit was cited. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as stale in August 2026 after years without implementation activity. A 2017 maintainer comment described the missing Yarn PATH exposure as intentional; no resolving PR or commit is cited. | |
| qwen/qwen3.6-35b-a3b | — | — | The nodejs plugin failed to expose yarn in $PATH, breaking postinstall scripts. Acknowledged as a mistake, the report was closed as stale without a fix. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
95
Support Request:
15
|
close stale | Nodejs plugin fails to add yarn to PATH during postinstall scripts, causing snap builds to fail. Issue is over 9 years old with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Nodejs plugin fails to add yarn to $PATH during postinstall scripts, causing snap builds to fail. Issue is over 8 years old with no maintainer interaction or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Nodejs plugin fails to add yarn to PATH during pull/build, causing postinstall scripts to fail. Issue is over 9 years old with no maintainer response or activity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft#1245
(confidence 90%)
Merged as commit 824a8ba79 to add Yarn support to the nodejs plugin, but it was not a fix for the reported PATH problem.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1639837 Missing yarn plugin | snapcraft (launchpad) | closed | Yarn support was added to the nodejs plugin rather than a standalone yarn plugin. PR canonical/snapcraft#1245 ('nodejs plugin: add support for yarn.') merged as commit 824a8ba79; issue closed 2017-04-08. |