Run details

NxWorkspace

CI Pipeline Executions
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Sign in

fix(oxlint): stop inferring a root project Nx itself does not create The previous fix stopped nested marker package.json files being promoted, but kept an escape hatch admitting the root package.json when the workspaces globs came back empty. That reopened the same failure class one level up. Empty globs mean Nx core creates no root project: core appends the root to the globs only when it carries an `nx` key, which `nx init` writes. So a root that genuinely is a project already arrives through the matcher, and the escape hatch only fired where Nx has no root project at all. Reproduced against real nx with the built plugin, in an integrated project.json monorepo with a root `src/`: root package.json without a name -> NX Failed to process project graph. The projects in the following directories have no name provided: - . same fixture, plugin unregistered -> graph fine root package.json with a name -> a phantom root project appears that `nx show projects` does not otherwise list Applies the matcher unconditionally, as core does. `should point a root project at ./src` was pinning the defect: its fixture is a root package.json with no `nx` key, i.e. one Nx creates no project for. Given the key, it describes a real standalone workspace and passes through the matcher branch. Adds a test for the integrated layout it could not cover.

nx affected -t e2e-macos-local --parallel=2 --base=c654db8137689921f377988e90c759bdb1502544 --head=b006e82929a0c48b573b9032fa5b42d9827cc315

Succeeded

3 CPU cores

read-write access token used

b006e82936491

95%

Cache hits

152 of 160 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

6 groups of tasks optimized.

© 2026 - Nx Cloud

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