← Back to issue list

Missing yarn plugin

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1639837
Type
issue
State
closed
Author
~elopio
Labels
new-plugin
Created
Updated
Closed

Current evaluation

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.

Resolution: closed resolved

Reason: Maintainer sergiusens closed the issue on 2017-04-08 pointing to snapcore/snapcraft#1245, which merged as commit 824a8ba79 ('nodejs plugin: add support for yarn.'). Yarn was integrated into the existing nodejs plugin instead of a separate plugin, per the earlier design discussion in the thread.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Yarn is a new cool way to handle nodejs dependencies: https://github.com/yarnpkg/yarn It replaces the npm client, but still uses the npm servers. It's massively popular in github, and many projects will start to use it, so we should support it.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved 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.
stealth/space-bunny-alpha — closed resolved Yarn support was added to the existing Node.js plugin rather than as a separate plugin via merged PR snapcore/snapcraft#1245 (commit 824a8ba79).
stealth/space-bunny-alpha — closed resolved Yarn support was added to the nodejs plugin by PR #1245 (commit 824a8ba79), resolving the missing-plugin request.
qwen/qwen3.6-35b-a3b — — Closed without implementation or comments. The request for a Yarn plugin was abandoned after over nine years, likely superseded by native dependency manager support.
qwen/qwen3.6-35b-a3b — — Requesting a Yarn plugin was closed without implementation. Zero comments were posted, and the feature request was abandoned due to prolonged inactivity.
qwen/qwen3.6-35b-a3b — — Feature request for a Yarn plugin was closed without implementation. No comments or development activity occurred, indicating the request was abandoned.
qwen3.6-35b-a3b-mtp-q6 — — The Yarn plugin request was closed without implementation, likely abandoned or superseded by native dependency manager support. No comments or resolution details were recorded.

Update history

Date Change
created

Related work

  • Likely Fixed By: canonical/snapcraft#1245 (confidence 98%)

    Merged PR adding yarn support to the nodejs plugin (commit 824a8ba79); cited by the maintainer when closing the issue.

  • Related To: snapcraft#1754 (confidence 70%)

    Commit 43a7b0fed 'nodejs plugin: pass proxy configuration to yarn (#1754)' is later follow-up work building on the yarn support.

  • Related To: snapcraft (launchpad)#1794727 (confidence 55%)

    Later open Launchpad report that yarn-based parts skip dependency install, showing the original yarn support was later removed with the node plugin's retirement in favour of craft-parts npm plugin.

Related issues

Issue Project State Summary Similarity
#1245 nodejs plugin: add support for yarn. snapcraft merged Merged Yarn support for Snapcraft's Node.js plugin in PR #1245 (commit 824a8ba79); the Yarn build test passed despite a Travis timeout.
84%
#1685551 When using yarn with the nodejs plugin, the yarn binary is not in $PATH snapcraft (launchpad) closed 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.
73%