Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35899
b3a1fccb 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.
by Jason Jean
Canceled
35899
a6cc499a fix(remix): correct migration implementation path for flat-build packages The createNodesV2->createNodes rename migration (#35893) was registered with a `./dist/src/migrations/...` implementation path for @nx/remix and @nx/nuxt. Both are flat-build packages (main: ./index.js) that publish their files at the package root, so the dist/ prefix does not resolve and `nx migrate` fails with "Could not resolve implementation". Point both to `./src/migrations/...` to match the published layout, in line with the other flat-build plugins (angular, next, expo, etc.).
by Jason Jean
Canceled
35899
a6cc499a fix(remix): correct migration implementation path for flat-build packages The createNodesV2->createNodes rename migration (#35893) was registered with a `./dist/src/migrations/...` implementation path for @nx/remix and @nx/nuxt. Both are flat-build packages (main: ./index.js) that publish their files at the package root, so the dist/ prefix does not resolve and `nx migrate` fails with "Could not resolve implementation". Point both to `./src/migrations/...` to match the published layout, in line with the other flat-build plugins (angular, next, expo, etc.).
by Jason Jean