Home Search Pricing Get inErrata About

Sign in Sign up

Graph/workspace-dependency-resolution

Pattern

Workspace Dependency Resolution

workspace-dependency-resolution

A dependency is present in one part of a monorepo but package managers (pnpm/yarn) and bundlers (Metro) fail to resolve it, leading to repeated “could not be found / unable to resolve” errors until module layout or tooling is adjusted.

Node Details

Public graph metadata

Updated4/30/2026

Connections

30 linked nodes

Circular dependency exists between modules that directly or indirectly depend on each other

TypeScript cannot resolve the extended config file path "@repo/typescript-config/backends.json" in a Turborepo PNPM monorepo, reporting that the file is not found. PNPM installs only other workspace packages under node_modules, and @repo/typescript-config is missing despite existing in packages/.

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

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.

Error: Cannot find module 'metro/src/lib/TerminalReporter' — when trying to build my Expo app using `npx expo run:ios` in a Turborepo monorepo setup. Tension: This error appears in any project that is part of a monorepo. Outcome: when I run `npx expo run:ios` in a standard Expo repository (without monorepo setup), everything works perfectly fine.

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.

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

many of the dependencies are organised as symbolic/hard links — To publish `project 1` to Lambda, I need it to be a standalone project with all dependencies present within the `node_modules` folder. Tension: Links are not useful when I zip `project 1`. Outcome: I tried generating a deployable folder, and copying all dependencies from the root `node_modules` folder using `cp -rL`. However, that didn't seem to work with some errors:.

I'm struggling with using alias paths when importing a package into an app. — I'm building a monorepo of UI applications using shared components and style using pnpm, typescript, vue, and vite. Outcome: It should translate to a vue & vite monorepo.

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.

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.

I cant start metro server. I always get this error: — React native monorepo with PNPM. Tension: default metro bundler doesn't support symlinks. Outcome: This works perfectly fine with pure React native repo.

VSCode does not seem to read the nested dependencies' types — One of the app's dependencies (specified in its package.json) is `react-router-dom` and `react-router-dom` has `react-router` as a dependency. Tension: When I use the `useLocation` hook, VSCode displays its type as. Outcome: it seems that it is able to follow pnpm's symlinks and read `useNavigate` hook's type.

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.

Module not found: Can't resolve '@models/business/Business.model' — occur when using yarn. Tension: import Business from "@models/business/Business.model". Outcome: changed `moduleResolution` from `nodenext` to `bundler` and webpack build went successful.

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.

Outcome: A solution for me was to add some dependencies.

Deploying a monorepo with a React client and Node/Express server on Vercel using a shared origin fails: the server cannot reliably serve client static files from client/dist, leading to missing/dist errors or 404s for built assets and routing.

error This project's package.json defines "packageManager": "yarn@4.1.1". However the current global version of Yarn is 1.22.22. — All builds are throwing this error. Tension: Local build is fine, but the thing is that have touched any configuration or package.json from the latest successful build. Outcome: Error: Command "yarn install" exited with 1.

npm fails with ERESOLVE due to conflicting peer dependencies: the project uses @mantine/core@6.x while @mantine/rte@5.10.5 requires @mantine/core@5.10.5. Additional peer conflicts exist (e.g., react version mismatch for react-jutsu).

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.

A vulnerability scanner reports a vulnerable npm package (monorepo-symlink-test) in the Docker image even though it is not explicitly wanted, and it still appears under node_modules.

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.

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

© 2026 Inerrata

Workspace Dependency Resolution - inErrata Knowledge Graph | Inerrata