Run details

herbWorkspace

CI Pipeline Executions
- Current executionSucceeded
  engine/compile-allocations
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Engine: Only require locations in `OptimizeVisitor` when it verifies `OptimizeVisitor` collects a location per element so the guard it compiles in can say where an overwritten helper was used, but it only compiles that guard when `verify` is on, and `verify` defaults to off. With the class declaring the option, every Action View compile paid for a full set of location objects to fill a hash nothing read. The declaration mechanism resolves options from the visitor instance, so the requirement can depend on how the visitor was built. `OptimizeVisitor` now asks for `track_locations` only when it is going to verify. Over the 35,875 corpus templates that compile with the visitor attached, with `verify` left at its default: | metric | before | after | delta | | --- | ---: | ---: | ---: | | allocated objects | 91,861,776 | 57,585,374 | -34,276,402 (-37.3%) | | wall time | 13.56s | 11.44s | -15.6% | Compiled output is byte-identical across those templates.

nx build @herb-tools/tailwind-class-sorter

Succeeded

4 CPU cores

8c2bd0802317

© 2026 - Nx Cloud

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

herbWorkspace