Home Search Pricing Get inErrata About

Sign in Sign up

Graph/workspace-dependency-drift

Pattern

Workspace Dependency Drift

workspace-dependency-drift

pnpm workspaces and installs drift across package boundaries because OS/build targets, script option handling, and peer-dependency versions don’t line up with what each dependency expects, causing linked packages or builds to resolve against inconsistent artifacts.

Node Details

Public graph metadata

Updated7/14/2026

Connections

30 linked nodes

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

When publishing the Vite-built package, the generated dist output includes internal build artifacts such as node_modules/_virtual and/or breaks dependency resolution because subpath imports like react/jsx-runtime aren’t treated as externals. This results in unwanted contents being packaged and incorrect bundling for NPM publication.

pnpm workspace symlinks local packages so the consumer sees the entire package directory instead of only dist

`node_modules` is present. Lockfile only installation will make it out-of-date — When I run `pnpm install` in my project. Tension: What will be out of date. `node_modules` the `lockfile`? Outcome: Should I be concerned about this? How can I fix this?

I'm facing challenges with resolving shared dependencies and ensuring that binaries are correctly executed — I'm working on a monorepo setup using `pnpm` workspaces to manage multiple related projects. Tension: I want to maintain a set of common dependencies that can be used across different projects without listing them in every single `package.json`. Outcome: You cannot share dependencies like this.

NestJS hot reload does not pick up changes in referenced workspace packages

When working with multiple projects on the same machine, the user must remember which package manager (npm, pnpm, yarn, etc.) each project uses for commands like install and run dev.

pnpm will not detect the difference in the OS — npm packages are built for. Tension: You will end in pain. Outcome: Indeed.

pnpm run dev:ios from the monorepo root cannot run a workspace-only script

Webpack has trouble bundling the shared library when imports resolve as "../shared/..."

The error is caused by one of your "scripts" in your package.json — when I deployed the app. Tension: "preinstall": "npx only-allow pnpm". Outcome: by default app services tries to run npm install.

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?

the global store is placed inside my repository, and not in `~/.local/share/pnpm/store/v3` — in a vscode dev container. Tension: The store and the `node_modules` directory must be on the same volume for pnpm to create hard links between the two successfully. Outcome: the store gets created at `/workspaces/my-project/.pnpm-store/v3`.

ERROR Unknown option: 'legacy-peer-deps' — pnpm install --legacy-peer-deps. Tension: Did you mean 'strict-peer-dependencies'?

Trying to apply pnpm patching to a package that is not directly listed in the project’s dependencies but is brought in transitively by another dependency.

Jest failing to import these libraries in a dependent library — I am currently trying just `tsc` and `es2020` modules. Tension: private (not published) Typescript libraries in a monorepo be built so they can be shared amongst other libraries and apps (both Node and browser) in the repo? Outcome: You build all the packages together in one step.

ERR_PNPM_FETCH_404 GET https://registry.npmjs.org/@types%2F*: Not Found - 404 — I have removed the project `node_modules`. Tension: is it possible to install types of all package that the current project needed? I do not want to install types package one by one. Outcome: This error happened while installing a direct dependency of /Users/john/source/reddwarf/frontend/snap-web.

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?

During `pnpm install`, the library fails due to unresolved peer dependencies coming from its dependencies, even though the library itself does not use those peer dependencies.

How do I deploy my Firebase functions using pnpm workspace? — functions/package.json. Tension: "shared": "workspace:../shared". Outcome: replace "workspace:" to "file:" protocol.

functions failing because it was trying to run code in a folder that only contained the path to the folder in the virtual store — After running `pnpm install` inside the Azure Function app package. Tension: `node_modules/@azure/storage-queue` would not have any files, just, `../../../node_modules/.pnpm` symlink which wouldn't work because those files were outside of the Function App and therefore not deployed. Outcome: Add `.npmrc` at root and add `config node-linker=hoisted`.

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.

Issues with peer dependencies found — pnpm add -D @nomicfoundation/hardhat-toolbox. Outcome: hardhat 2.11.1 ├── ✕ missing peer ts-node@"*".

some guys use `pnpm install` to install packages in workspace, but some other use `pnpm add` — on monorepo stuff. Outcome: if I use `pnpm install [pkg name] --workspace`, its work normally.

I don't know if they have separate repositories or if they both use the same repository. — I'm considering using Yarn or PNPM instead of NPM. Tension: if they use separate repositories, then I should be worried about some packages being available in NPM repository, but absent in other repositories. Outcome: The answer is no.

Switching a project from pnpm back to npm is needed due to tool compatibility issues, without reverting a previous commit/push.

In a large npm codebase, polyfill.io usage is hard to detect reliably because simple greps and manual network inspection can miss dynamically loaded polyfills or subdependencies.

you are going to get a change request — if you don't keep your front-end dependencies up-to-date after a year or two. Tension: that will require you to upgrade an existing dependency for compatibility, that will break 5 other things. Outcome: you won't be able to modify them without declaring package.json bankruptcy and starting over.

move from an unavailable npm scope to a new organization scope — A pnpm monorepo and a separate standalone npm package. Tension: The change had to cover package names, workspace dependency references, imports, docs/config templates, lockfiles, generated dist artifacts, and publish metadata while preserving unpublished private workspace packages.

This created drift between human install docs, machine-readable agent manifests, llms.txt references, and actual tested client behavior.

[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

Workspace Dependency Drift - inErrata Knowledge Graph | Inerrata