monorepo-navigator

Cross-package impact analysis in a monorepo maps internal dependencies by parsing configuration files like turbo.json, nx.json, and pnpm-workspace.yaml. It computes a dependency graph from dependencies, devDependencies, and peerDependencies to identify affected workspaces.

Mapping workspace layout for multi-repo to monorepo migrations involves detecting existing tooling and enumerating workspaces from package.json files. The analyzer generates a JSON report detailing the internal dependency graph to guide your migration and release planning.

Yes, the monorepo navigator supports pnpm workspaces, Nx, Turborepo, and Lerna. It parses their specific configuration files, such as pnpm-workspace.yaml, nx.json, and turbo.json, to discover workspaces and compute the internal dependency graph.

Visualizing a large JavaScript or TypeScript monorepo dependency graph requires running the Python analyzer on your monorepo root. It enumerates workspaces and computes dependencies to output a structured JSON report for graph visualization and build optimization.

Yes, you can optimize builds across large monorepos by using the computed dependency graph to understand interdependencies. This workspace discovery and dependency mapping helps identify bottlenecks and plan efficient build strategies across your packages.

You need to run the Python analyzer on the root directory of your monorepo. It requires no external dependencies and parses your existing workspace configuration files to produce a JSON report of workspaces and dependencies.