Home Search Pricing Get inErrata About

Sign in Sign up

Graph/pnpm

Component

pnpm

pnpm

pnpm

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0033

Connections

33 linked nodes

WRITTEN_INPackage

SUPPORTSPackage

jsii-code-samples

SUPPORTSPackage

node_modules/.pnpm/rxfire

SUPPORTSPackage

SUPPORTSPackage

SUPPORTSOperatingSystem

SUPPORTSPackage

AFFECTSRootCause

The issue occurred because the signing keys on https://registry.npmjs.org/-/npm/v1/keys were rotated — newly signed releases from pnpm caused Corepack to fail verification. Tension: In CI the problem can also affect older pnpm releases. Outcome: The issue is fixed in corepack@0.31.0 which is now rolled out to all supported versions of Node.js.

AFFECTSRootCause

We've replaced our .npmrc's auth_tokens with new ones — Weird because they haven't expired or anything. Tension: it was working fine but now at version 15 this happens. Outcome: and it's working again now.

AFFECTSRootCause

the order of the workspace packages define the build execution — The monorepo builds fine using standard `npm`. Tension: I remove the workspaces entry from the root `package.json` before running `pnpm`. Outcome: Try replacing `"@mydep/a": "link:../mydepb` in the package `b` package.json with `@mydep/a": "workspace:*"`.

AFFECTSRootCause

app services tries to run npm install. Tension: "preinstall": "npx only-allow pnpm". Outcome: this is what is causing the error.

I don't want to publish "app" package, just copy source code and run it something like `node app/index.js` — "app" depends on "lib" with the workspace protocol. Tension: This means I cannot use "pnpm publish". Outcome: Is it possible to manually trigger the workspace replacement manually?

AFFECTSRootCause

It looks like the filter uses the packages `name` — as defined in `package.json`. Tension: rather than its workspace directory. Outcome: following the `name` from `packages/starter/example/package.json`.

AFFECTSRootCause

add a script called "prepare" on package.json — packages/common/ui/package.json. Tension: pnpm run build. Outcome: prepare.

Is there an official blessed way to make this executable actually materialize somewhere so that I can execute it — package named `env-subset` that supplies an executable via the `bin` key in `package.json`.

it places only c dependency in example/node_modules — When I do pnpm install. Tension: it does not install necessary packages a and b. Outcome: That's the default and intended behavior of node_modules with pnpm.

AFFECTSRootCause

newly generated lockfile were different — If you remove the lockfile. Tension: newer versions of dependencies might be installed. Outcome: dependencies might be installed.

AFFECTSRootCause

Even if they used the same lockfile, there would be slight differences in how they work. Outcome: Each project needs to pick one package manager and stick to a given major version.

AFFECTSRootCause

Same option exists in `PNPM` using --filter "[<since>]" — legacy command using the `--since` option of `lerna`.

REQUIRESSolution

RUN npm install -g pnpm — modify line 115 in the bootstrap.sh file. Tension: npm install --loglevel verbose. Outcome: pnpm install --loglevel verbose.

REQUIRESSolution

If you need consistency between `node_modules` and `pnpm-lock.yaml`. Tension: especially in workspaces or deployments.

REQUIRESSolution

I just switched from npm to pnpm — Azure App Service. Tension: app services tries to run npm install.

REQUIRESSolution

pnpm --filter "@solana/wallet-adapter-example" build — following the `name` from `packages/starter/example/package.json`. Tension: pnpm --filter packages/starter/example run build. Outcome: Adding my own answer to help others:.

REQUIRESSolution

Install your package as a dependency of itself — pnpm add -D env-subset@link:.

REQUIRESSolution

Same option exists in `PNPM` using --filter "[<since>]" — `pnpm` to manage a monorepo from `lerna`. Tension: legacy command using the `--since` option of `lerna`.

REQUIRESSolution

Yarn registry is just a CNAME of `npm`. — I'm considering using Yarn or PNPM instead of NPM. Tension: separate repositories or if they both use the same repository. Outcome: visit the official yarn docs.

REQUIRESSolution

ERR_PNPM_ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE — The lockfile is broken! A full installation will be performed in an attempt to fix it. Tension: The lockfile is broken! A full installation will be performed in an attempt to fix it. Outcome: pnpm store prune && pnpm install.

PERTAIN_TOProblem

`ENOENT: no such file or directory, mkdir '/prod'` — I tried running pnpm deploy in many other folders. Tension: I tried to run in a folder that existed. Outcome: so I tried to run in a folder that existed.

PERTAIN_TOSolution

`pnpm why es5-ext` will work with pnpm — with pnpm. Tension: Is there an equivalent in pnpm? Outcome: See the docs: https://pnpm.io/cli/why.

OCCURS_ONProblem

it places only c dependency in example/node_modules — When I do pnpm install. Tension: it does not install necessary packages a and b. Outcome: That's the default and intended behavior of node_modules with pnpm.

OCCURS_INProblem

Linting and checking validity of types .Debug Failure. No error for last overload signature — after pnpm build. Tension: ELIFECYCLE Command failed with exit code 1.

OCCURS_INProblem

the "gcloud functions deploy" build process fails — in the monorepo I have local dependencies referencing "workspace:*". Tension: I have the obvious problem - in the monorepo I have local dependencies referencing "workspace:*". Outcome: Is there an elegant way to build and package my code so that "gcloud functions deploy" will have access to all the local dependencies it needs?

OCCURS_INProblem

Is there an official blessed way to make this executable actually materialize somewhere so that I can execute it — package named `env-subset` that supplies an executable via the `bin` key in `package.json`.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata