Home Search Pricing Get inErrata About

Sign in Sign up

Graph/workspace-symlink-build-mismatch

AntiPattern

pnpm Workspace Build Mismatch

workspace-symlink-build-mismatch

pnpm/workspace dependency resolution breaks builds because link/symlinked node_modules and option/argument handling differ from expectations, so bundlers (e.g., Rollup/PDF/canvas) and publish targets (e.g., Lambda) receive an incompatible artifact layout.

Node Details

Public graph metadata

Updated6/30/2026

Connections

30 linked nodes

MATCHESSolution

Try running — npm config set legacy-peer-deps true. Tension: npm ERR! ERESOLVE unable to resolve dependency tree. Outcome: npm config set legacy-peer-deps true.

MATCHESSolution

switching the node linker to hoisted mode — if that's not available in your environment. Tension: This changes the behaviour of PNPM to avoid creating symlinks.

MATCHESSolution

Add @repo/typescript-config as a devDependency (e.g., "@repo/typescript-config": "workspace:*") in the consuming app's package.json (apps/http-server), then reinstall dependencies with pnpm -w install so PNPM links the workspace package and TypeScript can resolve backends.json.

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

Starting with pnpm v10.9, installing JSR packages is natively supported — According to the Deno blog post Add JSR packages with pnpm and Yarn. Tension: pnpm-managed monorepo workspace. Outcome: pnpm add jsr:/.

MATCHESSolution

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

MATCHESSolution

Just paste this for a wacky fix — on my ubuntu wsl. Tension: pnpm fails (?) to find node in the $PATH and falls back to check /usr/bin/node. Outcome: `sudo ln -s /home/$USER/.nvm/versions/node/$(node -v)/bin/node /usr/bin/node`.

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

Try replacing `"@mydep/a": "link:../mydepb` in the package `b` package.json with `@mydep/a": "workspace:*"`. — in the package `b` package.json. Outcome: So the `b` package.json should become:.

MATCHESSolution

maybe try to change your ../src-tauri/tauri.conf.json the "build" section to this: — "build": {. Tension: I've tried changing beforeDevCommand between npm/pnpm and leaving it blank. Outcome: this worked for me.

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

I think you want the `--ignore-workspace` flag: — run pnpm on a nested package that is not supposed to be part of a workspace. Outcome: pnpm --ignore-workspace install.

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

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

MATCHESSolution

{ "pnpm": { "peerDependencyRules": { "ignoreMissing": ["typescript"] } } }. Tension: however for this small project i am not using typescript. Outcome: I just need to add this in my package json to remove the warning.

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

I switched over to yarn 1 (classic) workspaces and it worked. — I couldn't get it working with pnpm. Tension: I tried for way too long. Outcome: it worked.

MATCHESSolution

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

MATCHESSolution

multiple dependencies in a project require esbuild. Tension: separate dependencies require different versions of esbuild.

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

`pnpm add `: It will install one more package — in most cases they are interchangeable. Tension: there are some different options like `--offline` (for `install`)、`--workspace`(for `add`). Outcome: if choose yes i will use `pnpm add` because it is new modern syntax.

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

`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

Configure AWS Amplify to use the correct monorepo root/workspace (e.g., appRoot/workspaces/dashboard) and ensure install/build runs from that workspace so .next and the required server files are produced and packaged correctly.

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

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