Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
29132
5ddc6396 Changed admin-surface apps to build with Rolldown via rolldown-vite ref https://linear.app/ghost/issue/PLA-96 - adds a `rolldown` named catalog (vite: npm:rolldown-vite@7.3.1) and points the 8 admin-surface apps (posts, stats, admin, admin-x-framework, admin-x-settings, admin-x-design-system, shade, activitypub) at catalog:rolldown - public UMD apps stay on stock vite until their own Rolldown config lands (#29141) - the known Rolldown interop breakers are already fixed on main: shade Flag ESM swap (#29139), @svg-maps/world shim (#29143), @tryghost/i18n dual-format (#29144) - verified: all 8 apps + the admin shell build clean under Rolldown; react/react-dom stay external (no dual-instance regression); only benign bundler-agnostic warnings
by Steve Larson
Succeeded
29132
72fb03bd Bumped @vitejs/plugin-react to 5.2.0 for Rolldown-native JSX ref PLA-96 - Under rolldown-vite, plugin-react 4.7.0 ran JSX through the babel transform, emitting an invalid top-level "jsx" option warning and a [vite:react-babel] recommendation to switch to plugin-react-oxc. - plugin-react-oxc is now deprecated in favour of plugin-react v5+, which auto-detects rolldown-vite and routes JSX through the Oxc transform, so the admin-surface configs keep a bare react() call with no plugin swap. - Public UMD apps stay on stock vite@7.3.2 and fall back to the babel transform, which v5.2.0 still supports (vite ^7 peer).
by Steve Larson
Succeeded
29132
72fb03bd Bumped @vitejs/plugin-react to 5.2.0 for Rolldown-native JSX ref PLA-96 - Under rolldown-vite, plugin-react 4.7.0 ran JSX through the babel transform, emitting an invalid top-level "jsx" option warning and a [vite:react-babel] recommendation to switch to plugin-react-oxc. - plugin-react-oxc is now deprecated in favour of plugin-react v5+, which auto-detects rolldown-vite and routes JSX through the Oxc transform, so the admin-surface configs keep a bare react() call with no plugin swap. - Public UMD apps stay on stock vite@7.3.2 and fall back to the babel transform, which v5.2.0 still supports (vite ^7 peer).
by Steve Larson
Succeeded
29132
29be9105 Changed admin-surface apps to build with Rolldown via rolldown-vite ref https://linear.app/ghost/issue/PLA-96/spike-rolldown-vite-drop-in-build-benchmarks - Rolldown is a drop-in for the Rollup+esbuild pair Vite uses; the PLA-96 spike confirmed all 8 admin apps build and pass their test suites unchanged, with 5-8x faster production builds (admin 11.7s -> 1.4s) and byte-equivalent output - the 8 apps opt in by pointing their vite dep at a new `rolldown` named catalog (catalog:rolldown -> npm:rolldown-vite@7.3.1) so the opt-in is visible in each app's package.json; public UMD apps (portal, comments-ui, etc.) stay on the stock `vite` catalog because they carry bundler-specific config (e.g. portal's manualChunks:false) that Rolldown rejects and needs separate work - pinning rolldown-vite to the 7.x line (Vite 7 API) deliberately isolates the bundler swap from the Vite 8 API changes, which are a later step
by Steve Larson
Succeeded
29132
62b6a8d9 Changed admin-surface apps to build with Rolldown via rolldown-vite ref https://linear.app/ghost/issue/PLA-96/spike-rolldown-vite-drop-in-build-benchmarks - Rolldown is a drop-in for the Rollup+esbuild pair Vite uses; the PLA-96 spike confirmed all 8 admin apps build and pass their test suites unchanged, with 5-8x faster production builds (admin 11.7s -> 1.4s) and byte-equivalent output - the 8 apps opt in by pointing their vite dep at a new `rolldown` named catalog (catalog:rolldown -> npm:rolldown-vite@7.3.1) so the opt-in is visible in each app's package.json; public UMD apps (portal, comments-ui, etc.) stay on the stock `vite` catalog because they carry bundler-specific config (e.g. portal's manualChunks:false) that Rolldown rejects and needs separate work - pinning rolldown-vite to the 7.x line (Vite 7 API) deliberately isolates the bundler swap from the Vite 8 API changes, which are a later step
by Steve Larson