Run details

nx-examplesWorkspace

CI Pipeline Executions
- Current executionFailed
  dotnet/api-and-generated-types
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

refactor(types): configure codegen from package.json Per review on the blog post: for a TypeScript project, a package.json script is the more natural place for this than a project.json target. The command moves to `scripts.codegen` and the graph configuration to the `nx` block, so project.json goes away entirely. Two consequences worth knowing: - An inferred script runs with the project directory as its cwd, so the input path is relative to the library rather than the workspace root, and {projectRoot} no longer applies to it. The `outputs` entry still uses the token, since that is Nx config rather than the script. - Yarn only exposes binaries a workspace declares, so @hey-api/openapi-ts moves from the root to this library. It is the only project that runs it, so this is where it belongs. Claude-Session: https://claude.ai/code/session_01FMpiAGxMmARaZoonRd7Cov

nx-cloud record -- nx format:check --base=969a17b3745f7f80b186d1abe934438799021d45 --head=e82d38e6edbc50230d50573422743719adbcba6b

Succeeded

36 CPU cores

e82d38e6486

© 2026 - Nx Cloud

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

nx-examplesWorkspace