nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Current execution
Failed
feature/nxc-4312-add-oxlint-plugin
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(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-cloud record -- pnpm nx-cloud conformance:check
⌘K
Succeeded
nx-cloud record -- pnpm nx-cloud conformance:check
Click to copy
Linux
4 CPU cores
b006e829
36491
No resource usage was collected for this run.