Run details

NxWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/eslint-plugin-nested-package-json
- Runs and Agents
- Timeline
- Configuration
- Self-Healing CI
- Project Graph
- Resource Usage
- Analysis
- Conformance
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Sign in

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 affected --targets=lint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run,validate-example

Succeeded

03ab65de36510

94%

Cache hits

497 of 526 tasks used cache.

46%

Distribution saved time

9m 47s instead of 18m 00s.

Atomizer enabled

43 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools