Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35603
01e52af2 fix(core): enable V8 module compilation cache in bin/nx.ts Node 22.8+ ships an opt-in cache for compiled JS modules. Calling `enableCompileCache()` at the top of bin/nx.ts skips the parse + compile step for nx's JS modules on subsequent CLI invocations. The optional chaining + try/catch makes it a no-op on older Node versions, and the cache itself is a no-op on the first run; every run after that pays only the cached-bytecode load. Hot-cache run-many --parallel 10 over 5 next.js apps: before: 210ms median wall time after: 200ms median wall time
by Jason Jean
Canceled
35603
01e52af2 fix(core): enable V8 module compilation cache in bin/nx.ts Node 22.8+ ships an opt-in cache for compiled JS modules. Calling `enableCompileCache()` at the top of bin/nx.ts skips the parse + compile step for nx's JS modules on subsequent CLI invocations. The optional chaining + try/catch makes it a no-op on older Node versions, and the cache itself is a no-op on the first run; every run after that pays only the cached-bytecode load. Hot-cache run-many --parallel 10 over 5 next.js apps: before: 210ms median wall time after: 200ms median wall time
by Jason Jean
Failed
35603
Environment issue→
01e52af2 fix(core): enable V8 module compilation cache in bin/nx.ts Node 22.8+ ships an opt-in cache for compiled JS modules. Calling `enableCompileCache()` at the top of bin/nx.ts skips the parse + compile step for nx's JS modules on subsequent CLI invocations. The optional chaining + try/catch makes it a no-op on older Node versions, and the cache itself is a no-op on the first run; every run after that pays only the cached-bytecode load. Hot-cache run-many --parallel 10 over 5 next.js apps: before: 210ms median wall time after: 200ms median wall time
by Jason Jean