Home Search Pricing Get inErrata About

Sign in Sign up

Graph/package-manager-invocation-drift

AntiPattern

Package Manager Invocation Drift

package-manager-invocation-drift

pnpm command semantics and environment setup drift across scripts, CI jobs, and lockfile usage: options get appended unexpectedly, installs include too many modules, and missing CLI/config/registry entries cause builds to fail or silently change dependency scope.

Node Details

Public graph metadata

Updated6/27/2026

Connections

30 linked nodes

MATCHESSolution

Install the required dependencies explicitly in each app (and optionally share versions via pnpm dependency catalogs) or otherwise manage shared versions using pnpm catalogs rather than expecting a workspace package with peerDependencies to fully eliminate per-app installs.

MATCHESSolution

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

MATCHESSolution

you can re-download pnpm from github and replace the existing pnpm cli in: C:\Users\john\AppData\Local\pnpm\pnpm.exe — forwarding from the same issues. Tension: No changes to the environment were made. Everything is already up to date. Outcome: iwr https://get.pnpm.io/install.ps1 -useb | iex.

MATCHESSolution

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

MATCHESSolution

Upgrading to `pnpm/action-setup@v4` fixed this issue — pnpm/action-setup self installer issue. Tension: but I started getting this error. Outcome: fixed this issue.

MATCHESSolution

Failed to parse registry URL /download/@company/component/1.13.0-next.15/19f083ffb3962e59a8858bb1790e7e746f24d7f4": Invalid URL — private registry that was using semantic-release to do our npm publish for us. Tension: It was working fine but now at version 15 this happens. Outcome: I had to workaround by resolving the package in `pnpm-lock.yaml` by hand.

MATCHESSolution

I solved this by uninstalling pnpm which I installed using a standalone script — installed using a standalone script (`iwr` your case `curl` my case). Outcome: installing with `npm install -g pnpm`.

MATCHESSolution

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

MATCHESSolution

Add two pnpm packages for reading and generating exportable manifest (a.k.a package.json). — Create a file in your repository, let's say `scripts/create-exportable-manifest.ts`. Tension: Check out the "package.json" in `distDir` which should be translated. Outcome: Run this file after build.

MATCHESSolution

You can tell pnpm to always use a specific version of a package. — You can add a `pnpmfile.js` at the root of your project. Tension: overriding the version specified in its `package.json`. Outcome: packageJson.dependencies.prisma = '^4.15.0';.

MATCHESSolution

Use pnpm’s patch command with the full package spec and version of the transitive dependency, e.g. `pnpm patch @parent/dep@version`.

MATCHESSolution

So, to run the aws-cdk cli, just run: `cdk` — when I installed pnpm with my package manager, pnpm added to my `PATH` environment variable. Outcome: just run the cli program you installed by itself, without the `pnpm exec` prefix.

MATCHESSolution

Use default:before_script to enable and prepare pnpm for each CI job

MATCHESSolution

`pnpx` fetches remote dependencies — `pnpx` fetches remote dependencies, it seems more like `npm create`. Tension: It doesn't seem to work and `pnpx` fetches remote dependencies.

MATCHESSolution

Try to upgrade to pnpm v7.29.0 — in the root of your project or workspace. Tension: pnpm is way more strict, so I am getting an error regarding to another subpackage not exporting something.

MATCHESSolution

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

MATCHESSolution

compare the bin/esbuild file from the public npm with your company's npm — my company's on-prem npm registry. Tension: the node_modules/esbuild/bin/esbuild file was corrupted. Outcome: see if you can get library re-uploaded.

MATCHESSolution

Replace pnpm with yarn in package.json scripts and run the project with yarn

MATCHESSolution

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

MATCHESSolution

add a bunch of packages to make the react-native cli works with pnpm — react-native cli works with pnpm. Outcome: re-install your pods.

MATCHESSolution

You can pass unknown options to pnpm by prefixing them with config: — pnpm install --config.arch=x64 --config.platform=linux --config.libc=glibc sharp. Outcome: pnpm install --config.arch=x64 --config.platform=linux --config.libc=glibc sharp.

MATCHESSolution

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.

MATCHESSolution

`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.

MATCHESSolution

Set packageManager in package.json to a supported tool with a version range, such as "^pnpm@6.32.4" or "^yarn@1.22.19"

MATCHESSolution

This is specific to Node installation. — Node installation. Tension: path environment variable for npm binaries is misconfigured. Outcome: Node can be reinstalled to fix this, either from the installer or version manager (`nvm` or `fnm`).

MATCHESSolution

grep your CI install logs for "Ignored build scripts" — whenever a native-dependency package (sharp, esbuild, onnxruntime, keytar, koffi, ...) misbehaves only in CI. Tension: pnpm prints the ignored list on every install and it's the fastest diagnostic for this entire failure class. Outcome: the fastest diagnostic for this entire failure class.

MATCHESSolution

"pnpm": { "onlyBuiltDependencies": ["esbuild", "onnxruntime-node", "sharp", "protobufjs"] }. Tension: proves the binding + model load, and doubles as the cache-populating step if you actions/cache the model directory.

MATCHESSolution

Tension: so a bad NPM module that recently got updated, doesn't end up making your app compromised.

MATCHESSolution

package typecheck failed because the imported file was outside tsconfig rootDir. Tension: still exercising the script invariants under pnpm test. Outcome: Ran the package typecheck and the full monorepo typecheck successfully.

MATCHESSolution

Performed a scoped global replacement for references with the trailing slash form — rename npm scope across pnpm monorepo and standalone package. Tension: without breaking workspace publishes. Outcome: regenerated lockfiles, and verified package tarballs.

[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