NxEnterprise
    Nx
    fix(devkit): rename in-body usages in create-nodes-v2 type migration The rename-create-nodes-v2-types migration only rewrote the named bindings of import/export statements, leaving in-body references to a renamed binding dangling. A file like `export const createNodesV2: CreateNodesV2 = [...]` became `import type { CreateNodes }` with the annotation still reading `CreateNodesV2`, producing TS2552 "Cannot find name 'CreateNodesV2'". Track non-aliased import specifiers whose local binding changes and rewrite their in-body references too (type annotations and value usages), skipping member positions (foo.CreateNodesV2) and the import/export specifiers themselves. Aliased imports keep their local name, so they are untouched.
    nx affected --targets=lint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run
Sign in / Sign up
Succeeded
CI Pipeline Execution

nx affected --targets=lint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run

Click to copy
read-write access token used
61b76e3035899
<1%

Potential flaky tasks

2 of 586 tasks retried.

41%

Cache hits

241 of 586 tasks used cache.

95%

Distribution saved time

37m 13s instead of 12h 44m 17s.

Atomizer enabled

47 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools