node plugin doesn't run yarn install during build
Metadata
Current evaluation
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.
Suggested action: close stale
Reason: The nodejs plugin (which had yarn support added in #1245) has been removed and replaced by the npm plugin, as documented in docs/how-to/change-bases/change-from-core18-to-core20.rst ('The nodejs plugin is now npm'). A grep for 'yarn' across the current codebase returns zero matches, confirming yarn support no longer exists. The issue is 8 years old with no maintainer interaction and references a plugin that no longer exists.
Impact:
10
Quick Win:
7.5
Staleness:
95
Complexity:
25
Confidence:
85
Support Request:
10
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.8-27b |
Impact:
10
Quick Win:
7.5
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Node plugin reportedly skips yarn install during builds, causing failures. Open 7+ years with zero maintainer interaction or labels. Highly likely obsolete due to significant project and ecosystem evolution. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1685551 When using yarn with the nodejs plugin, the yarn binary is not in $PATH | snapcraft (launchpad) | closed | 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. |