In the nodejs plugin, there is no way to specify the npm version required
Metadata
Current evaluation
A dedicated npm plugin now supports selecting npm versions, resolving the legacy Node.js plugin limitation via craft-parts#200 (commit b9881154).
Resolution: closed resolved
Reason: The missing capability was implemented by the dedicated npm plugin added in craft-parts#200 at commit b9881154. The closing comment links Snapcraft 9 documentation confirming that npm versions can now be specified.
Evaluated by: mr-cal-bot
No scores available.
Issue body
From the dcos-ui project (https://github.com/dcos/dcos-ui):
"Node 4.x and NPM 3.x (and above) are required."
That is not possible with the nodejs plugin. when I use node v4.4.7, npm v2.15.8 is installed. I can use a more recent npm version by using a more recent node engine, but then the server won't start:
ERROR: Node version v6.7.x does not match required version v4.4.x
npm ERR! Linux 4.8.0-19-generic
npm ERR! argv "/snap/dcos-ui/x2/bin/node" "/snap/dcos-ui/x2/bin/npm" "run" "check-env"
npm ERR! node v6.7.0
npm ERR! npm v3.10.3
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | A dedicated npm plugin now supports selecting npm versions, resolving the legacy Node.js plugin limitation via craft-parts#200 (commit b9881154). | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved with the dedicated npm plugin, which supports specifying npm versions. craft-parts#200 added the plugin in commit b9881154. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by introducing a dedicated npm plugin that allows specifying npm versions independently, addressing the nodejs plugin limitation. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request to specify npm version independently in the nodejs plugin. Issue is nearly 10 years old with zero maintainer interaction or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
15
|
close stale | Feature request to independently specify npm version in the nodejs plugin. Issue is over 9 years old with no maintainer response or activity. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
15
|
close stale | Snapcraft nodejs plugin lacks independent npm version specification, causing conflicts when apps require specific Node and npm versions. Unaddressed for nearly a decade. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
craft-parts#200
(confidence 100%)
Added the dedicated npm plugin with configurable npm versions.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1955887 snapcraft npm doesn't respect npm-node-version | snapcraft (launchpad) | open | Legacy npm configuration was misleading: override-build bypasses the plugin-managed Node download; current craft-parts requires npm-include-node with npm-node-version. | |
| #1838474 nodejs plugin assumes a version key in the package.json | snapcraft (launchpad) | open | Legacy nodejs plugin crashed when package.json omitted its optional version field; active Snapcraft now uses the npm plugin and no longer contains that implementation. |