Skip to content

pnpm 12.19 adds a fund command and a smarter node linker

pnpm fund surfaces dependency funding links the way npm fund does, and the "loaded" node linker no longer needs you to list which packages require a build.

Source: pnpm

pnpm 12.19.0 shipped on 10 November. The headline addition is pnpm fund, which lists the funding URLs declared by installed dependencies, the same thing npm fund prints. It takes --json for npm-compatible output, --recursive or --filter to cover a workspace, a package name to open that package’s funding URL directly, and --which to pick between multiple funding options on one package.

pnpm fund
pnpm fund react --which=github

The loaded node linker also got smarter: packages that need a native build no longer have to be explicitly excluded, the linker now uses its side-effects cache to work out what needs building and skips redundant compiles across projects. Elsewhere, pnpm store add accepts a directory of tarballs and processes them recursively, there’s a prebuilt binary for NetBSD on x64, and credentials are no longer printed when an offline tarball fetch fails.

Why it matters: pnpm fund closes a small but real parity gap with npm, useful if your org tracks or sponsors dependency maintainers. The loaded linker change matters more day to day: anyone who has hand-maintained a list of packages needing builds can drop that list and let pnpm work it out.

Share

Related reading

More from The Wire

All briefs