Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35550
cbe89941 fix(core): pass packageManagerCommand from legacy plugins/package-json entry the legacy nx-all-package-jsons-plugin entry point at packages/nx/plugins/package-json.ts was missed in the earlier hoist; update it to compute the packageManagerCommand once and pass it as the required 5th argument to createNodeFromPackageJson, matching createNodesV2. fixes the TS2554 error in nx:build-base on CI.
by Jason Jean
Canceled
35550
cbe89941 fix(core): pass packageManagerCommand from legacy plugins/package-json entry the legacy nx-all-package-jsons-plugin entry point at packages/nx/plugins/package-json.ts was missed in the earlier hoist; update it to compute the packageManagerCommand once and pass it as the required 5th argument to createNodeFromPackageJson, matching createNodesV2. fixes the TS2554 error in nx:build-base on CI.
by Jason Jean
Failed
35550
Flaky task→
b47a98e5 cleanup(core): detect package manager once per createNodes invocation Inferred plugins were calling getLockFileName(detectPackageManager(...)) per project inside createNodesInternal. Hoist the detection to the createNodes callback alongside the existing pmc computation, derive both pmc and lockFileName from a single detectPackageManager call, and thread lockFileName through. Affects: angular, cypress, detox, expo, js/typescript, next, nuxt, playwright, react-native, remix, rollup, rsbuild, rspack, storybook, webpack.
by Jason Jean
Failed
35550
Fix available→
47a0c4e0 cleanup(core): hoist package manager command to createNodesV2 compute packageManagerCommand once per workspace at the createNodesV2 entry point and thread it through createNodeFromPackageJson and buildProjectConfigurationFromPackageJson into readTargetsFromPackageJson, instead of detecting per package.json read. addresses review feedback on #35550.
by Jason Jean
Failed
35550
Fix available→
47a0c4e0 cleanup(core): hoist package manager command to createNodesV2 compute packageManagerCommand once per workspace at the createNodesV2 entry point and thread it through createNodeFromPackageJson and buildProjectConfigurationFromPackageJson into readTargetsFromPackageJson, instead of detecting per package.json read. addresses review feedback on #35550.
by Jason Jean
Succeeded
35550
41078b69 fix(core): use workspace root for package manager detection in script targets readTargetsFromPackageJson received a workspaceRoot argument but never passed it to detectPackageManager / getPackageManagerCommand. Detection fell back to npm_config_user_agent, so the inferred npm run command on script targets depended on whoever invoked the process rather than on the actual workspace lockfile. The result was visible to users running nx in a workspace whose lockfile disagrees with their invoking shell's package manager. A module-level `let packageManagerCommand` cache also kept the first detection result across all subsequent calls in the same process, masking changes in workspaceRoot. Drops the module-level cache and threads workspaceRoot through to detection. The package-json create-nodes spec now seeds a package-lock.json into memfs (matching #35116's pattern for plugin specs) so the detector picks `npm` deterministically. Follow-up to #35116.
by Jason Jean