Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36510
fbc14e31 fix(linter): do not infer projects from package.json files outside the workspaces The plugin's glob includes `**/package.json`, and `splitConfigFiles` promoted every matching directory to a project root. Nested marker files — a `{"sideEffects": false}` next to a bundle, a polyfill directory's stub — have no `name`, so the whole graph then fails: NX Failed to process project graph. The projects in the following directories have no name provided: - packages/unenv-preset/src/runtime/polyfill Filter package.json files through the package manager's workspaces globs, the same guard Nx core's own package-json plugin applies. A package.json sitting next to a project.json is still a project regardless of the globs. When no workspaces are declared the filter is skipped entirely: the patterns come back empty and the matcher would reject everything, including the root package.json of a standalone repo that is itself the project. Verified against this repo: the 145-project graph is identical either way.
by Jason Jean
Failed
36510
Flaky task→
fbc14e31 fix(linter): do not infer projects from package.json files outside the workspaces The plugin's glob includes `**/package.json`, and `splitConfigFiles` promoted every matching directory to a project root. Nested marker files — a `{"sideEffects": false}` next to a bundle, a polyfill directory's stub — have no `name`, so the whole graph then fails: NX Failed to process project graph. The projects in the following directories have no name provided: - packages/unenv-preset/src/runtime/polyfill Filter package.json files through the package manager's workspaces globs, the same guard Nx core's own package-json plugin applies. A package.json sitting next to a project.json is still a project regardless of the globs. When no workspaces are declared the filter is skipped entirely: the patterns come back empty and the matcher would reject everything, including the root package.json of a standalone repo that is itself the project. Verified against this repo: the 145-project graph is identical either way.
by Jason Jean