Run details

NxWorkspace

CI Pipeline Executions
- Current executionSucceeded
  gh-36511
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

chore(nextjs): close gaps in the copied next helper import restrictions The no-restricted-imports override guarding the files copied into .nx-helpers replaces the package-level rule instead of merging with it, so anything it does not restate goes unenforced there. Adding src/utils/compose-plugins.ts to that override dropped the chalk, fs-extra and bare nx restrictions the file used to inherit. A top-level nx import emits require("nx") into the copied helper and fails on a pruned install the same way ./deprecation did, because update-package-json.ts never adds nx to the generated package.json. The relative-import patterns had a separate gap. They matched ./**/* and **/src/**/*, which cover plugins/with-nx.ts because it sits outside src, but let parent-relative specifiers through from a file inside src. Restate chalk and fs-extra, add the bare specifier to the nx group, and match `.`, `..`, `./**` and `../**` so any relative import is caught from either file. The glob forms need a path segment after the separator, so the two exact entries are what cover a bare `.` or `..`.

nx-cloud record -- pnpm nx-cloud conformance:check

Succeeded

4 CPU cores

c40b8fad36655

© 2026 - Nx Cloud

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

NxWorkspace