nx-import

To merge an external repository into an Nx monorepo, use a guided import workflow that pulls projects into target directories while preserving git history. This process aligns dependencies and ensures pnpm workspace globs and Nx naming conventions are respected for clean integration.

Importing an external app or library into an Nx workspace involves moving the project into apps/ or libs/ directories and adjusting pnpm workspace globs. You must merge dependencies and update nx.json settings to ensure the imported code integrates cleanly.

The best way to handle directory conflicts and dependency merging during an Nx workspace adoption is to use a structured import strategy. This approach checks for conflicts, merges dependencies, and cleans up stale files to maintain monorepo integrity.

Yes, post-import validation rehydrates Nx plugins and highlights fixes for ESLint, Jest, Vite, and Next.js configurations. This ensures executor paths and testing setups are correctly referenced after moving a project into the monorepo.

Common pitfalls when importing repositories into an Nx workspace include duplicate scripts, typecheck issues, plugin detection failures, and version conflicts. Risk mitigation tips help navigate these challenges and ensure a smooth repository merge.

Yes, nx-import supports both subdirectory-at-a-time and whole-repo workflows. These guided import strategies provide specific rules for applications versus libraries, ensuring directory conventions and Nx configuration requirements are met.