Nx
Enterprise
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-cloud record -- nx format:check
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx-cloud record -- nx format:check
Click to copy
Linux
4 CPU cores
61b76e30
35899