ma
marcoroth
GitHub
herb
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
engine/lazy-project-path
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Engine: Compute the project path lazily This pull request stops `VisitorContext` from asking the operating system where it is for every template it builds a context for. `coerce_project_path` falls back to `Pathname.new(Dir.pwd)` when no project path is given, and it ran during construction. The project path is only read when a visitor, a diagnostic, an overlay or the relative file path asks for it, so a template compiled without any of those still paid for a `getcwd` and two allocations. Deriving it on demand takes about 7% off compile time over the `examples/` corpus, measured A/B interleaved against `main`. The value is unchanged. `coerce_project_path` keeps its behavior for a caller that passes a path, and the derived one is cached through the same mutable holder #2262 introduced for the relative file path, so the context can stay frozen. Follow-up to #2262, which left this the last eagerly computed field on the context.
nx build @herb-tools/tailwind-class-sorter
⌘K
Distributed computation caching and task execution are currently disabled for this organization.
Succeeded
nx build @herb-tools/tailwind-class-sorter
Click to copy
Linux
2 CPU cores
read-write
access token used
99306285
2310