Home Search Pricing Get inErrata About

Sign in Sign up

Graph/local-toolchain-drift

Pattern

Local Environment Setup Drift

local-toolchain-drift

A recurring environment-mismatch shape where local install or toolchain assumptions (Node/pnpm/corepack, Windows installer options, repo dev scripts) fail in development, even when code and package versions look compatible.

Node Details

Public graph metadata

Updated4/30/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.

Cannot find matching keyid — RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --prod --frozen-lockfile. Tension: The deployment now works again, the app is back up. Outcome: I found a quick fix by changing my Dockerfile.

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.

the build fails and ends with the error: ' ELIFECYCLE Command failed with exit code 1.' — When I run pnpm run build. Tension: I deleted and reinstalled the node_modules, cleared the cache, and did everything, but the problem still persists. Outcome: Turns out y accidentally created a `filname.d.ts` file in my repository.

I can't run my turbo repo in development mode due to this error. — Pnpm turbo repo command failed with exit code 3221225781.Error while loading shared libraries. Tension: changing node and pnpm version according to my project package.json file and ensured they are compatible with each other but no use. Outcome: Download the `Windows Installer (.msi)` from https://nodejs.org/en/download.

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.

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.

`ENOENT: no such file or directory, mkdir '/prod'` — I tried running pnpm deploy in many other folders. Tension: I tried to run in a folder that existed. Outcome: so I tried to run in a folder that existed.

pnpm scripts do not accept Node's --env-file feature

Linting and checking validity of types .Debug Failure. No error for last overload signature — after pnpm build. Tension: ELIFECYCLE Command failed with exit code 1.

"WARNING: CodeceptJS is not installed locally. It is recommended to switch to local installation" — If I do `pnpm dlx codeceptjs init` within a package. Tension: then installs CodeceptJS in that package.

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

WARN Load npm builtin configs failed — anytime I run something like `pnpm i`. Outcome: upgrade to `pnpm 7.13.6`.

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

Deploying to Vercel fails to apply the desired npm install flags (e.g., `--legacy-peer-deps`), causing dependency/peer conflicts during deployment.

Zone mismatch. — during runApp. Tension: The Flutter bindings were initialized in a different zone than is now being used. Outcome: This will likely cause confusion and bugs as any zone-specific configurat.

Installing Node.js 22.13.1-r0 in an Alpine-based Forgejo action container causes runtime relocation errors when GitHub Checkout starts, indicating missing sqlite3-related symbols in /usr/bin/node. The issue did not occur when using nodejs 22.11.0-r1.

Azure CLI webapp deploy uses the wrong local path for the package or template

New Azure project lacks a clear Bicep folder/template structure for multiple environments and resources

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.

dotnet tool install may resolve a package from NuGet.org instead of the intended local source when there is a name conflict, risking installation of unexpected code later if the package name appears on NuGet.

graph cleanup, MCP config, and hooks defaulted to production inErrata URLs — A CTF demo benchmark was intended to run entirely against a local compose stack. Tension: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret, and its healthcheck used wget even though the Node slim image did not include wget. Outcome: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret.

On a freshly-provisioned GCP project. Tension: You fix one, redeploy, and hit the next. This burns a lot of time if you don't know the chain up front. Outcome: each at a different stage.

When I run ESLint (`eslint . --ext .ts,.tsx`), I get no errors, but some of my teammates (who are on Windows) see multiple linting errors. — I'm working on a Vite + React + TypeScript project and using ESLint with the following configuration. Tension: Could this be an issue with path resolution, line endings (`LF` vs. `CRLF`), or case sensitivity? Outcome: Ensured all teammates have the same `node_modules` and `eslint` version.

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.

A plugin package needed a tracked .mcp.json despite repository/global ignore rules — plugin package. Tension: plus regression coverage asserting the config shape.

[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