Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35897
0f42557a fix(repo): enforce import type in workspace-plugin via verbatimModuleSyntax @nx/workspace-plugin is type: module, so Nx loads its .ts files through Node's native type stripping, which can't erase a type imported as a value -- the plugin then fails to load (surfacing as the misleading "imported again after being required. Status = 0" on the swc-less FreeBSD publish job). Align the lib build to ESM (module/moduleResolution: nodenext) and enable verbatimModuleSyntax so a type-as-value import fails the build instead of only at runtime, and convert the remaining offenders to import type: ExecutorContext, ConformanceViolation (x2), and Tree (x2). This complements the copy-assets-plugin import type fix and prevents the whole class of bug from regressing across the package.
by Jason Jean
Canceled
35897
0f42557a fix(repo): enforce import type in workspace-plugin via verbatimModuleSyntax @nx/workspace-plugin is type: module, so Nx loads its .ts files through Node's native type stripping, which can't erase a type imported as a value -- the plugin then fails to load (surfacing as the misleading "imported again after being required. Status = 0" on the swc-less FreeBSD publish job). Align the lib build to ESM (module/moduleResolution: nodenext) and enable verbatimModuleSyntax so a type-as-value import fails the build instead of only at runtime, and convert the remaining offenders to import type: ExecutorContext, ConformanceViolation (x2), and Tree (x2). This complements the copy-assets-plugin import type fix and prevents the whole class of bug from regressing across the package.
by Jason Jean
Succeeded
35897
91d4b682 fix(repo): use import type for type-only @nx/devkit imports in copy-assets plugin CreateNodesV2 and TargetConfiguration are types but were imported as values. The @nx/workspace-plugin package is type: module, so under Node's native TypeScript stripping (Node >= 22.18) those names are left as runtime imports. @nx/devkit is CommonJS with no such runtime exports, so the plugin fails to load -- surfacing on the FreeBSD publish job as the misleading "imported again after being required. Status = 0" Node error. Marking them import type lets native strip erase them so the plugin loads on any Node.
by Jason Jean