← Back to issue list

node plugin doesn't run yarn install during build

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1794727
Type
issue
State
closed
Author
~lucyllewy
Labels
—
Created
Updated
Closed

Current evaluation

Closed as stale; node plugin no longer has explicit yarn support. Workaround provided by @ack using override-build to run yarn install manually.

Resolution: closed stale

Reason: Closed by @mr-cal as stale because the current plugins no longer have explicit support for yarn, and @ack provided a workaround using override-build to run yarn install manually.

Evaluated by: mr-cal-bot

No scores available.

Issue body

The node plugin for javascript applications provides an option to switch between using npm or yarn as the package manager for the part. The implementation seemingly doesn't run either `yarn install` or an equivalent process to fetch the application's dependencies prior to building. This results in either failed builds or builds that fail at runtime due to the missing dependencies.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — closed stale Closed as stale; node plugin no longer has explicit yarn support. Workaround provided by @ack using override-build to run yarn install manually.
stealth/space-bunny-alpha
Impact: 28
Quick Win: 10
Complexity: 34
Confidence: 86
Actionability: 52
close stale Yarn-based parts reportedly skipped dependency installation in the retired node/nodejs plugin; current Snapcraft uses the craft-parts npm plugin, which has no yarn option.
stealth/space-bunny-alpha
Impact: 52
Quick Win: 18
Complexity: 45
Confidence: 70
Actionability: 64
needs triage Yarn-based JavaScript parts reportedly build without dependencies; one user supplied an override-build workaround, but the unlabelled node plugin is absent from the current checkout and remains untriaged.
stealth/space-bunny-alpha
Impact: 55
Quick Win: 26
Complexity: 40
Confidence: 94
Actionability: 78
close resolved The legacy Node plugin skipped dependency installation; merged PR #762 moved it to the pull phase, but this report remains open with no discussion.
qwen/qwen3.8-27b
Impact: 10
Quick Win: 8
Staleness: 95
Complexity: 25
Confidence: 85
Support Request: 10
close stale Nodejs plugin yarn support bug from 8 years ago; the nodejs plugin has been removed and replaced by the npm plugin which only supports npm, so the reported yarn install issue is no longer applicable to the current codebase.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 10
close stale Node plugin fails to run yarn install during build, causing dependency fetch failures. Issue is unlabelled, has no maintainer comments, and has been inactive for nearly 8 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 85
Support Request: 10
close stale Unlabeled issue from ~7.8 years ago reporting that the node plugin fails to run yarn install during build, causing missing dependencies. No maintainer comments or activity in ~6.8 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 25
Confidence: 80
Support Request: 10
close stale Bug report stating node plugin skips yarn install during build, causing failures. Issue lacks labels, has zero comments, and has been inactive for over six years.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.