nxNx
GitHubNxWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      gh-36400
    • Runs and Agents
    • TimelineBeta
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
  • Sign in
    fix(vite): scope the alias length tiebreak to wildcards Ordering by prefix length also reordered two non-wildcard aliases that both matched only a prefix of the import, which is a shape TypeScript does not resolve at all: { "@repo": ["packages/broad"], "@repo/exact": ["packages/narrow"] } For `@repo/exact/thing` that flipped the answer from `packages/broad/exact/thing.ts` to `packages/narrow/thing.ts` while TypeScript, checked in all three module resolution modes, resolves neither. The tiebreak exists to implement TypeScript's longest-wildcard-prefix rule, so it now applies only where TypeScript applies it and everything else keeps the order it was declared in.
    nx affected --targets=lint,oxlint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run,validate-example
Succeeded
read-write access token used
7abf71d336424
1%

Potential flaky tasks

11 of 736 tasks retried.

17%

Cache hits

126 of 736 tasks used cache.

97%

Distribution saved time

55m 32s instead of 31h 36m 09s.

Atomizer enabled

49 groups of tasks optimized.

Resource usage is collected per agent

Run-level metrics are not available for distributed runs. View CPU and memory in this CI pipeline execution’s Analysis page.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubNxWorkspace