← Back to issue list

Add pnpm plugin

View original Github issue

Metadata

Project
snapcraft
Number
#6080
Type
issue
State
open
Author
steinbro
Labels
Status: Triaged
Created
Updated
Closed
—

Current evaluation

Feature request to add a pnpm plugin so snaps can build Node.js projects using pnpm instead of npm. Triaged and endorsed by maintainers (Jira SNAPCRAFT-1306); no pnpm support exists in the codebase yet.

Suggested action: keep open

Reason: The issue is explicitly triaged (`Status: Triaged`), authored by maintainer steinbro, endorsed by @bepri ('I second this'), and tracked internally as SNAPCRAFT-1306. Grep for 'pnpm' across the repo returns zero matches and `git_log_search` for 'pnpm' finds no commits, confirming it is unimplemented rather than already fixed. Comparable plugins landed repeatedly in this repo (uv #5196, Poetry #5090), so the precedent and design pattern are established, and the ask is unambiguous with an identified consumer (signal-desktop).

Evaluated by: mr-cal-bot

Impact: 52 Quick Win: 23 Complexity: 45 Confidence: 84 Actionability: 82

Issue body

### Check existing issues - [x] I've verified that this request isn't described by any existing issues. ### Request [pnpm](https://pnpm.io/) is a faster, more modern alternative to npm that is growing in popularity for Node.js projects. ### The problem it solves This would be useful in snaps for codebases that use it, such as [signal-desktop](https://github.com/snapcrafters/signal-desktop/blob/candidate/snap/snapcraft.yaml).

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 52
Quick Win: 23
Complexity: 45
Confidence: 84
Actionability: 82
keep open Feature request to add a pnpm plugin so snaps can build Node.js projects using pnpm instead of npm. Triaged and endorsed by maintainers (Jira SNAPCRAFT-1306); no pnpm support exists in the codebase yet.
qwen/qwen3.6-35b-a3b
Impact: 45
Quick Win: 15
Complexity: 55
Confidence: 80
Actionability: 75
keep open Feature request to add a pnpm plugin to snapcraft/craft-parts for Node.js projects using pnpm instead of npm. Issue is triaged and open.
qwen/qwen3.8-27b
Impact: 45
Quick Win: 25
Staleness: 55
Complexity: 45
Confidence: 80
Support Request: 10
keep open Feature request to add a pnpm plugin to snapcraft, modeled on the existing npm plugin in craft-parts. Labeled triaged with internal Jira ticket SNAPCRAFT-1306 created, but no implementation progress for about 6 months.
qwen/qwen3.6-35b-a3b
Staleness: 65
Complexity: 45
Confidence: 75
Support Request: 10
keep open Feature request to add a pnpm plugin for Snapcraft, labeled triaged but inactive for over 4 months with no maintainer follow-up or implementation progress.
qwen3.6-35b-a3b-mtp-q6
Staleness: 65
Complexity: 40
Confidence: 90
Support Request: 10
keep open Feature request to add a pnpm plugin for snapcraft to support modern Node.js package managers. Triaged and acknowledged by maintainers, with an internal tracking ticket created. Awaiting implementation prioritization.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft#5196 (confidence 70%)

    Commit800823a55 'feat: support for the uv plugin (#5196)' is the closest precedent — a new package-manager build plugin wired through snapcraft/parts/plugins/ and documented in the changelog.

  • Blocked By: craft-parts (confidence 55%)

    The npm and uv plugin implementations live in craft-parts (UvPlugin here subclasses `craft_parts.plugins.uv_plugin.UvPlugin` and overrides `_get_system_python_interpreter`), so the core pnpm build logic likely needs upstream work before Snapcraft can register a wrapper.

Related issues

No related issues found above the similarity threshold.