de
Default
GitHub
nxext
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
chore/upgrade-nx-23
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
fix(e2e): fix ignoreDeprecations drift breaking 5 e2e projects in CI `ignoreDeprecations: '6.0'` in the shared legacy-workspace tsconfig was wrong for every locally-installed TypeScript (5.9.3 only accepts "5.0"), but `create-nx-workspace@latest` floats to whatever npm currently ships as latest — which had moved to a real TypeScript 6.0 major, where the same deprecations require "6.0" instead. No single literal satisfies both, so pin the e2e workspace's typescript to the range every @nxext/* package already declares in peerDependencies (^5.7.3) instead, and set ignoreDeprecations back to "5.0" to match. That pin then surfaced a second, previously-masked bug: svelte-preprocess 5.1.4's TS5-migration compat shim auto-injects the now fully-removed `importsNotUsedAsValues` compiler option whenever it sees `ignoreDeprecations: "5.0"`, which TypeScript 5.9 rejects outright (TS5102). svelte-preprocess 6.x dropped that shim in favor of auto-setting `verbatimModuleSyntax`, so bump the generator's pinned version. Fixes ionic-angular-e2e, preact-e2e, svelte-e2e, stencil-e2e, and solid-e2e failing in the Nx Cloud distributed CI run for PR #1201 while passing locally — the fresh npm install each of these e2e specs performs is exactly what made the drift CI-only. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xpn3tnTKhe4Pd8grXphQPg
nx-cloud record -- pnpm exec nx format:check
⌘K
Succeeded
nx-cloud record -- pnpm exec nx format:check
Click to copy
Linux
4 CPU cores
b3cdbdfe
1201
GitHub
nxext
Workspace