link-workspace-packages

Fix TS2307 cannot find module errors in a monorepo by linking workspace packages with native dependency declarations instead of tsconfig path aliases. This adds the correct local symlink so sibling package imports resolve properly during TypeScript builds.

Link a new package to an existing workspace using pnpm or yarn by adding the sibling package via your package manager's native workspace syntax. This creates the correct local symlink and declares the dependency automatically without manual package.json edits.

The best way to resolve missing imports for local packages in a monorepo is using native workspace-aware linking rather than manual package.json edits. This establishes real symlinks and correct dependency declarations for sibling packages across npm, yarn, pnpm, and bun.

Yes, this workspace linking approach works with pnpm and bun workflows, alongside npm and yarn. It applies each package manager's native workspace syntax to create correct local symlinks and dependency declarations for sibling packages.

Use native workspace syntax instead of tsconfig path aliases because path aliases are brittle and do not create actual symlinks. Native workspace linking adds real dependency declarations that satisfy module resolution across your entire monorepo build pipeline.

Broken workspace package resolution occurs after generating new packages because the sibling packages lack proper local dependency declarations and symlinks. Linking them with your package manager's native workspace syntax fixes these missing imports and module resolution failures.