← Back to issue list

snapcraft npm doesn't respect npm-node-version

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1955887
Type
issue
State
open
Author
~nanu
Labels
snapcraft
Created
Updated
Closed

Current evaluation

npm part ignores npm-node-version: build runs Node v10.19.0 instead of requested 14.13.0, breaking a vue-cli build. No maintainer activity or comments in ~4.7 years; npm part since moved to craft-parts where the property is supported.

Suggested action: close stale

Reason: The issue is 1708 days old with 0 comments, no labels, and no maintainer interaction, and it targets the core18/core20-era npm part that has since been moved to the craft-parts library, where npm-node-version is a documented, supported property — so the original problem is no longer reproducible in current versions. Confidence is reduced because repository tooling failed (no pinned SHA) and I could not confirm the current npm part implementation in code.

Impact: 35 Quick Win: 21.0 Staleness: 92 Complexity: 40 Confidence: 45 Support Request: 15

Issue body

I have this code and it always tells me v10.19.0. That's bad because vue cli needs a more recent version: ``` You are using Node v10.19.0, but vue-cli-service requires Node ^12.0.0 || >= 14.0.0. Please upgrade your Node version. ``` ``` axolotl-web: plugin: npm source: ./axolotl-web npm-node-version: 14.13.0 override-build: | # Due to the confinement this runs as root, and then we need this config nodejs --version npm config set unsafe-perm true npm ci npm run build mkdir -p ../install/bin cp -r dist ../install/bin/axolotl-web stage: - bin/axolotl-web ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 21.0
Staleness: 92
Complexity: 40
Confidence: 45
Support Request: 15
close stale npm part ignores npm-node-version: build runs Node v10.19.0 instead of requested 14.13.0, breaking a vue-cli build. No maintainer activity or comments in ~4.7 years; npm part since moved to craft-parts where the property is supported.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 10
close stale snapcraft npm plugin ignores npm-node-version config, defaulting to Node 10. User provided a snapcraft.yaml snippet and vue-cli error. Issue has zero comments and no maintainer response after over 4 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 25
Confidence: 85
Support Request: 10
close stale Snapcraft's npm plugin ignores the npm-node-version property, defaulting to Node v10.19.0 instead of the specified version. Issue is untriaged with no maintainer activity for over 4 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 45
Confidence: 85
Support Request: 10
close stale Snapcraft npm plugin ignores npm-node-version setting, defaulting to Node v10.19.0 and breaking vue-cli builds. Issue has been inactive for over 4.5 years with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 35
Confidence: 80
Support Request: 10
needs triage snapcraft npm plugin ignores the npm-node-version property, defaulting to Node v10.19.0 instead of the specified v14.13.0. Untriaged and inactive for over four years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 10
close stale Report that snapcraft's npm plugin ignores the npm-node-version property, causing Node version mismatches during build. Issue is 4.5 years old with no maintainer response.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.