workspace-dependency-check

pnpm workspace module resolution fails when local package names are mismatched, pnpm-workspace.yaml paths exclude the target package, or main and exports fields point to non-existent files. This skill diagnoses these specific configuration mismatches to identify the root cause.

To fix missing workspace dependencies in a pnpm monorepo, you must validate consumer package.json dependencies and ensure pnpm-workspace.yaml includes the target package path. This skill inspects these configurations and suggests concrete fixes for stale dependencies.

Validating package.json exports fields requires checking that main and exports paths point to existing files and align with consumer expectations. This skill verifies these fields against your local workspace setup to resolve misconfigured package imports.

Module not found errors in pnpm workspaces are caused by incomplete workspace definitions, incorrect package.json names, or misaligned exports fields. This skill diagnoses these resolution failures by inspecting your workspace configuration and package metadata.

Yes, this workspace diagnosis supports monorepos with complex package structures by validating local package names, pnpm-workspace.yaml paths, main and exports fields, and consumer dependencies across the workspace to ensure proper module resolution.

When pnpm-workspace.yaml paths do not resolve local packages, you must verify the paths include the target package and match the directory structure. This skill validates your workspace configuration and suggests corrections for incomplete definitions.