nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
fix/eslint-plugin-nested-package-json
Runs and Agents
Timeline
Configuration
Self-Healing CI
Project Graph
Resource Usage
Analysis
Conformance
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
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.
nx-cloud record -- nx sync:check
⌘K
Succeeded
nx-cloud record -- nx sync:check
Click to copy
Linux
4 CPU cores
03ab65de
36510
No resource usage was collected for this run.