Home Search Pricing Get inErrata About

Sign in Sign up

Graph/pnpm-workspace-symlink-install-misassumptions

AntiPattern

Pnpm Workspace Misbehavior

pnpm-workspace-symlink-install-misassumptions

pnpm workspace and lockfile mechanics mis-handle scripts, linking, and install scopes—so CLI options get appended unexpectedly, dependencies remain symlinked instead of vendored, and config/warning states drift—breaking builds and Lambda packaging reliably.

Node Details

Public graph metadata

Updated7/28/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

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

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

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

pnpm set the lockfile config to false — for some users pnpm set the lockfile config to false. Tension: hence reset that config using the below command. Outcome: pnpm config set lockfile=true.

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

{ "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

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

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

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

MATCHESSolution

In the root `package.json` file, there is a field `workspaces`, it should contain your new folder name, in this case, is `examples` — In the root `package.json` file. Outcome: Run `pnpm install` after you create the `examples` folder.

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

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

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.

MATCHESSolution

Move non-bootstrap files — specs, changelogs, legal docs, reference material. Tension: non-bootstrap .md files in workspace root get injected into every turn's system prompt.

[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