Home Search Pricing Get inErrata About

Sign in Sign up

Graph/workspace-alias-drift

AntiPattern

Workspace Package Alias Drift

workspace-alias-drift

Package manager semantics drift across pnpm workspaces and devcontainer OS versions, causing dependency resolution and script/build options to behave differently than expected; builds link unpredictably, toolchains (e.g., svgo) break on missing flags, and “aliasing” becomes a fragile workaround.

Node Details

Public graph metadata

Updated7/25/2026

Connections

30 linked nodes

MATCHESSolution

Either avoid modifying shadcn-managed component files and instead extend/wrap them in separate components, or accept that re-running the npx install will overwrite `tsx/ts` changes and then manually re-apply any customizations when desired.

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

Aligning the package versions usually fixes the issue — between 2 packages in your repository. Tension: a different version of the "zod" dependency. Outcome: either manually or by using a tool like ncu. You can also move common dependencies into your root package to enforce a common version.

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

Configure `.syncpackrc` to handle only the special case (local monorepo packages/workspace protocol), e.g., add a version group that pins `$LOCAL` dependencies to `workspace:*` for `packages: ['**']`. Then rely on Syncpack’s default behavior to discover and sync the versions of shared dependencies like react/react-dom and related @types across apps.

MATCHESSolution

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

MATCHESSolution

If you want a way to share dependencies, you could also check Bit workspace — share dependencies the way you want. Tension: Bit has environment components, which allow to share dependencies the way you want. Outcome: Bit has environment components.

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

different versions of devcontainer's OS lead to different versions of compiled dependencies — When I migrate another Apps, I might need another Debian version. Tension: this would lead to the packages land in the sam. Outcome: I figured out later.

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

I just switched from npm to pnpm — Azure App Service. Tension: app services tries to run npm install.

MATCHESSolution

Instead of using VSCode's `Reopen in Dev Container`, I used `Clone Repository in Container Volume`. Tension: an isolated Docker volume with no bindings. Outcome: pnpm was then happy to use parent directories for the store.

MATCHESSolution

Use selective dependency resolutions to force all `gesto` dependency instances to resolve to `file:packages/gesto` (via `resolutions` with Yarn, or `resolutions` plus `npm-force-resolutions` in an npm `preinstall` script).

MATCHESSolution

Configure matching alias paths in root and app tsconfig files

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

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

`svgo` will fail without `stable` — If you remove `stable`, `svgo` won't run, because it uses stable. Tension: how to also exclude it from package resolution to avoid PNPM WARN? Outcome: npm i boidolr/svgo#remove-stable.

MATCHESSolution

After many hours bashing my head against this, I ended up just using the package name itself as an alias.

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

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

An alternative might be to use Paket. — NuGet uses a pessimistic version resolution strategy. Tension: This should give you more up-to-date transitive package versions. Outcome: the lock file should prevent unwanted updates.

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

Hardened migration/model-ref resolution — the deprecated provider id is treated only as a legacy alias for the CLI runtime. Tension: stale refs are canonicalized to Anthropic model refs, old allowlist keys are removed, and external CLI OAuth sync recognizes the legacy alias. Outcome: external CLI OAuth sync recognizes the legacy alias.

[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

Workspace Package Alias Drift - inErrata Knowledge Graph | Inerrata