mrkeyoor.comAsk

pnpm/pnpmtested 09 Oct 2026commit 3c4ebe3

pnpm review

Our pnpm repository install succeeded in 46 seconds, but the runner skipped both build and test steps, leaving correctness unassessed.

  • 1 packages
46 sto install
    Dev Toolsevaluationupdated 20 Oct 2026
    +53stars / 7d

    pnpm manages the packages used by JavaScript projects and can link related projects inside one repository. Its shared package storage reduces duplication, while stricter dependency access helps expose imports that a project forgot to declare.

    Verdict

    Our pnpm repository install succeeded in 46 seconds, but the runner skipped both build and test steps, leaving correctness unassessed. Choose pnpm for explicit workspace dependencies and shared package storage if you can check the change against your own application. That evidence supports a trial, not a claim that pnpm will beat another package manager on your workload.

    We ran it

    Lab card: what happened when we ran pnpm
    Lab card from our sandbox run
    Screenshot of pnpm (pnpm.io)
    pnpm.io
    Install✓ · 46s1 packages · 9 MB
    Buildn/ano build script
    Testsn/ano test script
    Repo9168 files~1,331,539 lines of source · 63.8 MB · 29 CI workflows

    Answers from our run

    Does pnpm build from source?

    Dependencies installed in 46 seconds (1 packages), and the project has no separate build step. We cloned commit 3c4ebe3 into a clean Debian container with 3 CPUs and no project-specific setup.

    Does pnpm have tests you can run?

    Not through a standard command: the project exposes no test script or target that our harness could run.

    Who should not use pnpm?

    Applications that depend on importing undeclared packages and whose owners cannot change their manifests: pnpm deliberately restricts dependency access.

    What are the alternatives to pnpm?

    npm, Yarn. Our pnpm repository install succeeded in 46 seconds, but the runner skipped both build and test steps, leaving correctness unassessed.

    Setup4/5Our source checkout installed in 46 s with 1 dependency, but we did not run a README task.Editor’s note: The detected install succeeded, but raw runtime logs and an application migration were unavailable for a supported-environment setup assessment.
    Docs4/5Editorial rubric: 4/5 for explaining installation prerequisites, local dependency resolution and workspace limits; those instructions were not reproduced end to end.
    Community5/5Last push on 2026-10-20 and 37,083 stars.Editor’s note: The current push and combined issue/PR queue were inspected, but maintainer response times and support outcomes were not assessed.
    Maturity4/5Latest release v12.14.0 on 2026-10-15 and repository created 2016-01-28.Editor’s note: Build and test targets were skipped by the runner, and this run did not assess the correctness or compatibility of published artifacts.

    How we score

    Discussed on

    1. hnhttps://github.com/pnpm/pnpm: 404 Not Found4 points
    2. hnNPM retires audit endpoint; breaks pnpm audit4 points
    3. hnpnpm 94 points
    4. hnPNPM vs Yarn: monorepo node_modules4 points
    5. hnpnpm 73 points

    Who it’s for

    Maintainers of JavaScript workspaces who want local package relationships made explicit through the workspace: protocol.
    Developers keeping several projects on one machine who want package files shared through a common store.
    Teams prepared to fix undeclared imports and check their release process before changing package managers.

    Who it’s NOT for

    Applications that depend on importing undeclared packages and whose owners cannot change their manifests: pnpm deliberately restricts dependency access.
    Workspaces that require guaranteed dependency-ordered script execution despite circular package relationships: the workspace documentation explicitly excludes that guarantee.
    Platforms without a pnpm 12 binary whose operators require the current native release: the installation guide directs those targets to JavaScript pnpm 11.
    Organizations requiring the entire checkout to be MIT-licensed: the README excludes pnpr/, which uses the PolyForm Shield License.

    Setup reality

    Our sandbox installed pnpm's repository at commit 3c4ebe3 in 46 seconds on October 9, 2026, recording 1 dependency and 9 MB on disk. Build and test steps were skipped because the runner found no corresponding script or target. This establishes a successful detected install, with no compiled or tested result.

    The basic public-package workflow does not call for a hosted account or API key. Adoption needs a package-manager version pin, pnpm-lock.yaml, and workspace configuration where packages share a repository. Access to private registries requires their own authentication.

    Current documentation describes pnpm 12 as a native executable. Its npm-based installer requires Node.js 22.13 or newer, although the installed executable does not need Node.js itself. Our recorded sandbox had 3 CPUs, 8g RAM and image lab-node:22; that label does not identify the actual runtime or operating system.

    Declared dependencies are the reason to consider pnpm

    An application that imports a package missing from its own package.json is exactly the sort of project pnpm asks you to repair. The README describes restricted dependency access alongside a shared package store and pnpm-lock.yaml. For a maintainer, the attraction is a dependency graph you can explain: application code should name what it uses, and local packages should resolve where you expect.

    That makes pnpm worth considering when a JavaScript repository is becoming several interdependent projects. It also sets the migration cost. If your application survives through accidental access to another package's dependencies, moving the install command alone won't settle the change. Someone must correct those declarations. I'd choose pnpm for a team willing to own that work, especially when shared local packages already cause confusion.

    What happened when we ran it

    Our sandbox install succeeded in 46 seconds, recording 1 dependency and 9 MB on disk. We ran commit 3c4ebe3 on October 9, 2026, with 3 CPUs and 8g RAM. The recorded image was lab-node:22. Without the raw toolchain logs, that image name cannot establish the actual Node.js version or operating system.

    The checkout contained 9,168 files, roughly 1,331,539 source lines and 63.8 MB of repository content. Build and test stages were skipped because the runner found no corresponding script or target. With only 1 dependency recorded against that tree, the result gives little coverage of the monorepo. It does not establish that the full repository can be built or that its tests pass.

    The scan found 29 CI workflow files, monorepo workspaces, no Dockerfile and no tests directory. Those are discovery results from this checkout. A missing directory does not establish that upstream has no tests. Nor can this run compare npm, Yarn and pnpm speed: it records one installation path without a competing workload or controlled cache comparison.

    The shared store helps when projects reuse package files

    pnpm's README describes a content-addressable store, with project files linked through hard links or copy-on-write reflinks. Identical package content can therefore be reused across projects on a disk. This is a concrete reason to consider pnpm on a developer machine that accumulates repositories with overlapping dependencies.

    The size of the saving depends on that overlap and your storage layout. Our 9 MB installation record does not quantify savings against npm or Yarn, and it should not become a projected saving for your laptop. Try the packages you actually keep around. Shared storage is useful even when you have no reason to care which installer wins a stopwatch comparison.

    workspace: makes a local package requirement explicit

    The workspace documentation gives a practical distinction. With ordinary version ranges and workspace linking enabled, a matching local package can be linked, while an unavailable local version can come from the registry. The workspace: protocol instead requires local resolution. A missing matching package causes failure rather than an unexpected registry substitution.

    For example, a dependency written as workspace:2.0.0 requires that local version. This is a documented example, not a command reproduced in our sandbox. When packages are packed or published, pnpm converts workspace references into ordinary version specifications. Consumers can then use their own package manager. That combination suits repositories that develop packages together but release them separately.

    Circular relationships remain a boundary. pnpm's docs say dependency cycles prevent a guarantee that scripts execute in dependency order. If your release process relies on that ordering, map the cycle before adopting the tool. A new lockfile cannot repair the relationship between the packages.

    pnpm 12 separates its executable from the npm installer

    The installation guide describes pnpm 12 as native. Once installed, the executable does not require Node.js, although installing it through npm requires Node.js 22.13 or newer. Your JavaScript application still has its own runtime requirements. Keeping those requirements separate avoids rejecting pnpm simply because an application's runtime differs from the installer's prerequisite.

    The guide lists prebuilt platforms and directs targets without a binary to JavaScript pnpm 11. It also recommends the npm route on Windows because Defender may block the standalone executable. Choose the route for your actual workstation and CI platform. Pin the package-manager version before asking colleagues to reproduce the setup.

    npm and Yarn each have a reason to stay

    npm comes bundled with Node.js and most third-party distributions. Keep it when the existing workflow works and you cannot name a package-storage or workspace problem worth a migration. Yarn supports workspaces and plugins, so an existing Yarn extension is a concrete reason to investigate keeping that investment. Neither choice loses this comparison on speed: our run provides no comparative timing evidence.

    Documentation earns 4/5 here on an editorial rubric: it explains prerequisites, local resolution and specific workspace limits, while this run did not reproduce those instructions end to end. Setup ease and maturity remain unassessed. GitHub's metadata recorded an October 20, 2026 push and 189 open issues and PRs; that combined queue alone cannot establish support quality, so community also remains unassessed.

    Check licensing if you distribute the checkout: the README places pnpr/ under PolyForm Shield while the rest is MIT. Then trial pnpm on a representative application branch, including a packed local package and the deployment path. The useful result is a dependency graph your team can release without surprises.

    Alternatives

    ProjectWhat it isPick it when
    npm gh↗A JavaScript package manager bundled with Node.js and most third-party Node distributions.pick this instead when your existing Node distribution and package workflow already meet the project's needs.
    YarnA package manager with native workspace support and a plugin system.pick this instead when your repository depends on Yarn plugins or you want to extend package management through its Node API.

    What people are saying

    1. [github-trending] pnpm/pnpm

    Sources

    1. pnpm README
    2. pnpm installation and supported platforms
    3. pnpm workspace resolution and publishing
    4. npm CLI README
    5. Yarn README
    6. pnpm public repository metadata

    More dev tools reviews