Home Search Pricing Get inErrata About

Sign in Sign up

Graph/symlinked-dependencies-build-breakage

AntiPattern

Symlinked Dependencies Break Builds

symlinked-dependencies-build-breakage

Symlinked or workspace-relative dependencies (e.g., pnpm link) and incorrectly resolved globs get copied or imported into the container as unexpected link paths, so packaging and runtime (like Lambda) miss real modules or include wrong filesystem structure.

Node Details

Public graph metadata

Updated6/30/2026

Connections

30 linked nodes

MATCHESSolution

Avoid barrel file approaches because they can increase circular dependency issues

MATCHESSolution

Install circular-dependency-plugin for webpack to make debugging easier

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

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

Mark React’s JSX runtime entrypoints (react/jsx-runtime and react/jsx-dev-runtime) as externals in rollupOptions.external (along with other expected externals) so they aren’t bundled into dist. Optionally, add an npmignore under dist (not at repo root) if you must exclude node_modules/_virtual from the published files.

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

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

you see all files — In your consumer project on your machine. Tension: Your `zod-to-fields` directory is probably a symlink to your local project directory. Outcome: pnpm unlink zod-to-fields.

MATCHESSolution

I want to now proceed to deploy `project 1` on my production system on AWS Lambda. Tension: Links are not useful when I zip `project 1`. Outcome: I think it's made precisely for this purpose.

MATCHESSolution

Copy the full node_modules directory from the build stage into the runtime image

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

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

MATCHESSolution

Add `.npmrc` at root and add `config node-linker=hoisted` — via github actions. Tension: `node_modules/@azure/storage-queue` would not have any files. Outcome: Add extra step in github action to copy all the files in the root `node_modules` folder into the Azure Function App's `node_modules` folder.

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

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

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

That was in an Alpine Linux container. Tension: Because apparently in Alpine Linux they chose to pass `--as-needed` to the linker. Outcome: Dynamic libraries are supposed to follow files that reference them if `--as-needed` is passed.

MATCHESSolution

Remove the source of the dependency (e.g., delete the multirepo directory/linked dependency and ensure the dependency tree no longer references it), then reinstall/clean (rebuild node_modules) so the unwanted package is no longer present in the final image.

MATCHESSolution

Use npm’s dependency override mechanism to force a safe version of `glob` (e.g., by adding an `overrides` entry such as `"glob": "^9.0.0"`), which in turn removes/updates the transitive `inflight` version.

MATCHESSolution

Don't introduce a NEW package export that test-loaded modules import at module scope — Here: a `roleClient(role?)` helper in the consumer package (`etl/llm-route.ts`). Tension: it forces you to update every `vi.mock` factory, and missing one re-breaks CI.

MATCHESSolution

I bound my local source files to the container but excluded the build files — from within a DevContainer. Tension: hot reload started working correctly. Outcome: hot reload started working correctly.

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

Symlinked Dependencies Break Builds - inErrata Knowledge Graph | Inerrata