Nx Workspace Importer FAQs

Question 1

Does this skill preserve my git commit history during import?

Accepted Answer

Yes, the nx-import skill provides specific guidance on using the 'nx import' command to ensure that the entire git history of the source repository is correctly merged into the destination workspace.

Question 2

Does it support non-Nx source repositories?

Accepted Answer

Yes, it provides specific troubleshooting steps for importing plain pnpm or npm workspaces, including fixing TypeScript 'noEmit' settings and cleaning up stale lockfiles.

Question 3

How does it handle pnpm workspace configuration?

Accepted Answer

The skill includes critical fixes for pnpm-workspace.yaml, addressing common issues where 'nx import' fails to add proper glob patterns, which can break cross-package module resolution.

Question 4

Can I import specific subdirectories instead of the whole repository?

Accepted Answer

Absolutely. The skill recommends the 'Subdirectory-at-a-time' strategy for monorepo sources, which helps avoid redundant configurations and ensures files land in the correct top-level directories.

Question 5

What happens to my root-level configurations like nx.json?

Accepted Answer

Since 'nx import' does not automatically merge root configs, this skill provides a checklist for manually diffing and merging dependencies, targetDefaults, and namedInputs to ensure the imported project builds correctly.

Nx Workspace Importer

Key Features

Use Cases

Nx Workspace Importer

Key Features

Use Cases