← Back to issue list

npm plugin: Support `disable-parallel` parameter

View original Github issue

Metadata

Project
craft-parts
Number
#1246
Type
issue
State
open
Author
lengau
Labels
Type: Enhancement Status: Needs information
Created
Updated
Closed
—

Current evaluation

Feature request to add the disable-parallel part property to the npm plugin. Labeled Needs information; maintainers await a real-world use case before implementing. No activity for ~12 months; part of a family of similar open issues for other plugins.

Suggested action: keep open

Reason: The issue is explicitly triaged (Type: Enhancement, Status: Needs information) and the body itself frames it as a tracked low-priority enhancement: 'extremely low priority until someone shows us a real-world use case.' The npm plugin still lacks the property at HEAD (verified in npm_plugin.py), so it remains applicable rather than obsolete; it is one of ten sibling tracking issues for the same property across plugins, so closing it would lose the tracking. It should stay open but remain low priority until a use case appears.

Impact: 15 Quick Win: 10.5 Staleness: 65 Complexity: 30 Confidence: 85 Support Request: 5

Issue body

### What needs to get done Support the [disable-parallel](https://canonical-craft-parts.readthedocs-hosted.com/latest/common/craft-parts/reference/part_properties/#disable-parallel) part property in the npm plugin. ### Why it needs to get done All of our plugins should theoretically support this. In practice though, this is extremely low priority until someone shows us a real-world use case for it. If someone can bring us a real-world use case that we can test against (especially a case of "this application simply does not build with parallel"), that would be ideal. The [autotools plugin](https://github.com/canonical/craft-parts/pull/1167) required this for OpenJDK builds, for example.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 15
Quick Win: 10.5
Staleness: 65
Complexity: 30
Confidence: 85
Support Request: 5
keep open Feature request to add the disable-parallel part property to the npm plugin. Labeled Needs information; maintainers await a real-world use case before implementing. No activity for ~12 months; part of a family of similar open issues for other plugins.
qwen/qwen3.6-35b-a3b
Staleness: 80
Complexity: 35
Confidence: 85
Support Request: 5
close stale Enhancement request to add disable-parallel parameter support to the npm plugin. Currently unaddressed and awaiting a real-world use case from contributors.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 80
Support Request: 5
close stale Request to add disable-parallel support to the npm plugin. Labeled enhancement and needs information, but has seen no maintainer comments or user responses in over 10 months.
qwen3.6-35b-a3b-mtp-q6
Staleness: 80
Complexity: 25
Confidence: 80
Support Request: 5
close stale Add disable-parallel parameter support to the npm plugin. Currently stalled pending a real-world use case or testable build failure. Status requires additional information before proceeding.

Update history

No update history recorded yet.

Related work

  • Related To: craft-parts#1244 (confidence 90%)

    Same feature for the maven-use plugin.

  • Related To: craft-parts#1242 (confidence 90%)

    Same feature for the make plugin.

  • Related To: craft-parts#1237 (confidence 90%)

    Same disable-parallel feature requested for the go plugin; open, awaiting a use case.

  • Related To: craft-parts#1232 (confidence 90%)

    Same feature for the ant plugin; open, inactive, awaiting a use case.

  • Related To: craft-parts#1240 (confidence 90%)

    Same feature for the java plugin.

  • Related To: craft-parts#1247 (confidence 90%)

    Same feature for the python plugin; maintainers discussing a 3-state design, also Needs information.

  • Related To: craft-parts#1236 (confidence 90%)

    Same feature for the dotnet (v2) plugin.

  • Related To: craft-parts#1239 (confidence 90%)

    Same feature for the gradle plugin.

  • Related To: craft-parts#1235 (confidence 90%)

    Same feature for the dotnet plugin.

  • Related To: craft-parts#1167 (confidence 85%)

    Autotools plugin PR that first added disable-parallel support (OpenJDK builds), cited in the issue as the precedent.

Related issues

Issue Project State Summary Similarity
#1232 ant plugin: Support `disable-parallel` parameter craft-parts open Feature request to add the disable-parallel part property to the ant plugin. Labeled 'Needs information' and waiting ~1 year for a real-world use case; maintainer explicitly called it extremely low priority until one is provided.
86%
#1243 maven plugin: Support `disable-parallel` parameter craft-parts open Feature request to add the disable-parallel part property to the maven plugin. Labeled 'Needs information' - maintainer awaits a real-world use case. No activity for ~12 months; the maven plugin still lacks the property.
85%
#1238 go-use plugin: Support `disable-parallel` parameter craft-parts open Feature request to add the disable-parallel part property to the go-use plugin. Labeled Needs information; maintainer awaits a real-world use case, none provided in ~12 months. Plugin still lacks the property.
83%
#1244 maven-use plugin: Support `disable-parallel` parameter craft-parts open Feature request to add the disable-parallel part property to the maven-use plugin. Labeled 'Needs information' by the maintainer, who asked for a real-world use case; no comments or use case provided in 12 months.
83%
#1235 dotnet plugin: Support `disable-parallel` parameter craft-parts open Request to add the disable-parallel part property to the dotnet plugin. Labeled Needs information; the maintainer marked it extremely low priority pending a real-world use case, which has not been provided in 363 days.
83%
#1250 rust plugin: Support `disable-parallel` parameter craft-parts open Feature request to add the disable-parallel part property to the rust plugin. Labeled 'Needs information' — maintainer awaits a real-world use case before implementing. No activity for 363 days; rust plugin still lacks the property.
82%
#1251 scons plugin: Support `disable-parallel` parameter craft-parts open Request to add the disable-parallel part property to the scons plugin. Labeled 'Needs information' by the maintainer, who called it extremely low priority until a real-world use case is provided; no use case or activity in ~12 months.
82%
#1233 cargo-use plugin: Support `disable-parallel` parameter craft-parts open Feature request to add disable-parallel to the cargo-use plugin. Labeled Needs information; maintainer awaits a real-world use case, none provided in ~12 months. Plugin still lacks the property; its build step is a file copy, so the property would be a no-op.
81%
#1240 java plugin: Support `disable-parallel` parameter craft-parts open Enhancement request to add the disable-parallel part property to the Java base plugin (shared by ant, gradle, maven, maven-use). Labeled Needs information; maintainer awaits a real-world use case, no activity for 363 days.
81%
#1245 meson plugin: Support `disable-parallel` parameter craft-parts open Request to add the disable-parallel part property to the meson plugin, mirroring the autotools implementation. Labeled 'Needs information' and waiting on a real-world use case; no activity for ~12 months and the feature is still unimplemented.
80%