pnpm

The pnpm repository has 35K stars!

RFC about native monorepo versioning in pnpm: github.com/pnpm/rfcs/pull… based on changesets with additional features on top

@Bodok0 pnpm v12 will not have any breaking changes.

Bro I had just updated my projects to v11

It's friday so took the time to sponsor some of the OSS dependencies we rely on @trylatitude We are now proud sponsors of @honojs @biomejs @pnpmjs @DrizzleORM @vitest_dev Knipjs

@geclos @trylatitude @honojs @biomejs @DrizzleORM @vitest_dev Thanks!

@stanzillaz If some commands don't work yet, you can actually mix different versions. You can run "pnpm with 11 outdated" for instance. Or vice versa: pnpm with next-12 install

looking forward to testing this, just needs the `--store-dir` PR to get in then we can go brrrr

If you are on the latest pnpm v11.10.0 (or v10.34.5), you can try out the pnpm v12 alpha via: pnpm self-update 12.0.0-alpha.5 It is fully in Rust! 🦀

pnpm v11.10 is out! github.com/pnpm/pnpm/rele…

@lahar0n Because you can only do server side resolution if the registry is developed by the package manager. Expect every package manager do the same in the coming months.

@pnpmjs why would you do that just use jsr

Very early sneak peek to pnpr - the pnpm registry: pnpm.io/pnpr/

@Otakulihao @jiahan_c you can use the rust rewrite. It should be much faster, we just need to fix this issue with the command shim: github.com/pnpm/pnpm/pull…

@jiahan_c @pnpmjs are we loosing something if using node —run instead of pnpm run?

Small CI tip: On Node.js 22+, use `node --run <script>` instead of `pnpm run <script>` for simple package scripts in GitHub Actions. Tiny change, saves 200-400ms per call.

pnpm v11.9 is out! github.com/pnpm/pnpm/rele…

@thugz001 In 2026 this is like asking "Did you use a computer to write the code?"

@pnpmjs Use AI rewrite or not？

Work on installation is mostly done in the pnpm Rust rewrite. Now we are doing all the other commands. If you want to pick something up, here is the roadmap: github.com/pnpm/pnpm/issu…

@_AlicanAkyildiz It is in progress. You can try it via this package: @pnpm/pacquet" target="_blank" rel="nofollow noopener">npmx.dev/package/@pnpm/…

@pnpmjs when v12

pnpm v11.8 is out! github.com/pnpm/pnpm/rele…

When coderabbit approves the pr, it gets tagged and we get a message on discord

If you contribute to pnpm, you increase your chance at a getting a human review once @coderabbitai approved the changes

The downloaded Node.js and pnpm artifacts are cryptographically verified against their signatures. If you commit the lockfile, their contents are additionally verified against the integrity hashes recorded in the lockfile. pnpm is the only package manager that records integrity hashes for the runtime and package manager themselves in the lockfile, enabling an additional layer of verification that other setup actions don’t provide.

@pnpmjs Do you have a good reason/documentation to why this over node + corepack enable pnpm? Having a hard time justifying the additional risk.

We have created a new GitHub action that you can use to setup both pnpm and a JS runtime - node, deno, or bun: github.com/marketplace/ac…

@lumusika Well surprise, npm cli will block scripts by default too

@pnpmjs Siempre lo usé, pero desde la versión 10+ da problemas con versiones de librerías usadas en Nestjs y tuve que volver a npm. Tal vez debería tener una base de datos de librerías seguras para correr sus scripts en Frameworks seguros como Nest, Angular y bloquear el resto.

The pnpm rust engine can now do resolution too. If you install the latest @pnpm/pacquet with pnpm v11.7, pacquet will also do resolution on top of fetching and linking. pnpm add @pnpm/pacquet@0.11.7 --config

@stanzillaz ok, it will be checked

@pnpmjs this still seems to be a thing on 11.7, not sure if that was supposed to work yet though #issuecomment-4682732058" target="_blank" rel="nofollow noopener">github.com/pnpm/pnpm/issu…