Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
22.6.x
5771eb33 fix(react-native): use vite's transformWithEsbuild instead of direct esbuild import The react-native vite config template imported esbuild directly, which fails during project graph processing in pnpm strict mode because esbuild is only a transitive dependency of vite and not hoisted to root node_modules. Fixes e2e-detox:e2e-macos-local failure.
by Colum Ferry
Succeeded
master
36534a42 fix(angular-rspack): ensure rebuild chunks emitted summary accurate (#34979) ## Current Behavior Currently, rebuilds produce a summary table that is not accurate. A key difference in how Rspack sets `chunks.rendered` compared to Webpack resulted in the logic for determining rebuilt chunks to be incorrect. ## Expected Behavior Ensure the summary table for emitted chunks is accurate on rebuild ## Related Issues It does not _fully_ solve #34936, however it should be a good first step to finding out if too many chunks are being emitted
by Colum Ferry
Succeeded
22.7.0-beta.4
36534a42 fix(angular-rspack): ensure rebuild chunks emitted summary accurate (#34979) ## Current Behavior Currently, rebuilds produce a summary table that is not accurate. A key difference in how Rspack sets `chunks.rendered` compared to Webpack resulted in the logic for determining rebuilt chunks to be incorrect. ## Expected Behavior Ensure the summary table for emitted chunks is accurate on rebuild ## Related Issues It does not _fully_ solve #34936, however it should be a good first step to finding out if too many chunks are being emitted
by Colum Ferry
Succeeded
master
36534a42 fix(angular-rspack): ensure rebuild chunks emitted summary accurate (#34979) ## Current Behavior Currently, rebuilds produce a summary table that is not accurate. A key difference in how Rspack sets `chunks.rendered` compared to Webpack resulted in the logic for determining rebuilt chunks to be incorrect. ## Expected Behavior Ensure the summary table for emitted chunks is accurate on rebuild ## Related Issues It does not _fully_ solve #34936, however it should be a good first step to finding out if too many chunks are being emitted
by Colum Ferry
Succeeded
34979
744ff8cd fix(angular-rspack): ensure rebuild chunks emitted summary accurate
by Colum Ferry
Failed
master
732a08c7 chore(core): build nx to local dist and use nodenext (#34111) ## Current Behavior The `nx` package compiles its TypeScript output to `../../dist/packages/nx/` (relative to the package root), which places build artifacts outside the package directory at the repo root level (`dist/packages/nx/`). This makes the package structure harder to reason about, complicates the build pipeline, and doesn't align with how most packages organize their output. The package uses `"module": "commonjs"` with basic module resolution, which limits future migration paths toward ESM. ## Expected Behavior The `nx` package now builds to a local `dist/` directory within the package itself (`packages/nx/dist/`). This is a cleaner, more standard layout — like having your tools in your own toolbox instead of scattered across the workshop. ### Key changes: **Build configuration (`packages/nx/tsconfig.lib.json`):** - `outDir` changed from `../../dist/packages/nx` to `dist` (local to package) - `module` changed to `nodenext` with `moduleResolution: nodenext` - Updated `include` patterns to explicitly list source directories **Package entry points (`packages/nx/package.json`):** - `bin` paths updated: `./bin/nx.js` → `./dist/bin/nx.js` - Added `"type": "commonjs"` explicitly - Added comprehensive `exports` map with `@nx/nx-source` condition for dev/test resolution back to TS source - Added `postinstall` path update to `./dist/bin/post-install` **Module resolution fixes:** - Created `src/utils/handle-import.ts` — a CJS-first import utility that falls back to ESM `import()` for ESM-only packages, providing a single migration point for future ESM work - Converted dynamic `await import()` calls to `require(require.resolve())` pattern where needed to satisfy `nodenext` extension requirements - Plugin worker spawn path now uses correct `.ts`/`.js` extension based on runtime context (source vs compiled) **Test infrastructure:** - Added custom `jest-resolver.js` for the `nx` package that resolves `nx/...` imports using the `@nx/nx-source` exports condition, so tests run against TS source - Updated `jest.preset.js` with SWC transformer configuration - Added chalk mock for test compatibility **CI and tooling:** - Conformance check updated to build `workspace-plugin` first (the Nx Cloud runner lacks `@swc-node/register` for TS resolution) - Conformance rule paths in `nx.json` now point to compiled `dist/workspace-plugin/src/...` output - Added `dist` to eslint ignore patterns to prevent linting compiled output - Added workspace-plugin build target and updated its dependencies **Other fixes:** - Various import path fixes across `create-nx-workspace`, gradle, and other packages to work with `nodenext` resolution - Updated e2e test paths to reference the new dist location - Fixed `.gitignore` and `.npmignore` for the new output structure ## Related Issue(s) Internal infrastructure improvement — no external issue. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: Coly010 <Coly010@users.noreply.github.com> Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
by Colum Ferry
Failed
34111
55e90182 fix(react-native): use vite's transformWithEsbuild instead of direct esbuild import The react-native vite config template imported esbuild directly, which fails during project graph processing in pnpm strict mode because esbuild is only a transitive dependency of vite and not hoisted to root node_modules. Fixes e2e-detox:e2e-macos-local failure.
by Colum Ferry
Succeeded
34111
a1b82259 fix(react-native): use vite's transformWithEsbuild instead of direct esbuild import The react-native vite config template imported esbuild directly, which fails during project graph processing in pnpm strict mode because esbuild is only a transitive dependency of vite and not hoisted to root node_modules. Fixes e2e-detox:e2e-macos-local failure.
by Colum Ferry
Canceled
34111
Environment issue→
8e3989d2 chore(core): ignore the temp vite files
by Colum Ferry
Failed
chore/nx-local-dist
e549e9ae chore(core): fix project-graph import
by Colum Ferry
Failed
34111
Generating fix→
87cc68f9 chore(core): fix project-graph import
by Colum Ferry
Failed
34111
Fix ready→
2a5af0e5 =chore(core): redeploy netlify
by Colum Ferry
Failed
34111
Environment issue→
1d40bbeb chore(core): update lockfile
by Colum Ferry
Failed
34111
Environment issue→
1d40bbeb chore(core): update lockfile
by Colum Ferry
Failed
34111
035a4d80 =chore(core): redeploy netlify
by Colum Ferry
Failed
34111
035a4d80 =chore(core): redeploy netlify
by Colum Ferry
Failed
34111
606eb0cb =chore(core): redeploy netlify
by Colum Ferry
Canceled
34111
be719435 =chore(core): redeploy netlify
by Colum Ferry
Failed
34111
Fix applied→
d10dcfc4 chore(core): fix exports
by Colum Ferry
Failed
34111
Fix applied→
358416f9 chore(core): fix exports
by Colum Ferry