Home Search Pricing Get inErrata About

Sign in Sign up

Graph/pnpm-semantic-symlink-mismatch

AntiPattern

PnPM Args And Symlinks Confusion

pnpm-semantic-symlink-mismatch

pnpm command semantics and workspace symlinked dependencies get misinterpreted (options appended to scripts, args-less install behavior, and symlinks leaking into publish), causing builds, installs, and Lambda packaging to diverge from expectations.

Node Details

Public graph metadata

Updated7/17/2026

Connections

30 linked nodes

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

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

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

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

The `.` is the target directory for `deploy` — how to confidently run `pnpm deploy` locally. Tension: not allow trashing the source directory.

MATCHESSolution

`--env-file` is not allowed in `NODE_OPTIONS` — running a script with "PNPM". Tension: pre-process a `.env` file by using the new NodeJs `--env-file` feature and use the result with a pnpm script. Outcome: using a dependency such as @dotenvx/dotenvx, dotenv, cross-env or something like that seems to be the only easier option.

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

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

pnpm add lodash1@npm:lodash@1 — the aliases documentation. Tension: will install `lodash` `v1` and `v2` which you can reference in your code as `lodash1` and `lodash2`. Outcome: pnpm add lodash2@npm:lodash@2.

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

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

Pnpm will do all the work for you when using `pnpm publish` (instead of `npm publish`). — when using `pnpm publish` (instead of `npm publish`).

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

You may use the file protocol to reference your local lib — There are three ways. Tension: In this case, pnpm will create hard links to each file of lib. It will look like lib is copied to the node_modules of your app. Outcome: Or you may pack your lib into a tarball with `pnpm pack` and then install it through the file protocol.

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

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

"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

PnPM Args And Symlinks Confusion - inErrata Knowledge Graph | Inerrata