Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Failed
master
18557f8a docs(misc): various updates embedding videos in docs pages
7 hours ago by jaysoo
Failed
33349
2525e989 fix(misc): use .cts extension in jest config path for Jest 30 Updates update-workspace.ts to detect Jest version and use jest.config.cts path in project configuration when Jest 30+ is detected, matching the actual file that gets created by the generator. Also updates e2e-project test snapshots to expect CommonJS syntax.
7 hours ago by jaysoo
Canceled
33349
aca0a5bc chore(misc): fix js tests
7 hours ago by jaysoo
Failed
33349
1218682a chore(misc): fix angular tests
9 hours ago by jaysoo
Failed
33349
a07b0f01 chore(misc): fix e2e tests
10 hours ago by jaysoo
Canceled
33349
416f9fa9 chore(misc): update executor spec to use jest.config.cts
10 hours ago by jaysoo
Failed
33349
a07b0f01 chore(misc): fix e2e tests
13 hours ago by jaysoo
Canceled
33349
66fd0ee1 chore(misc): fix react-native
13 hours ago by jaysoo
Canceled
33349
67e63a06 chore(misc): fix express and nest
13 hours ago by jaysoo
Failed
33349
23821632 chore(misc): fix next
14 hours ago by jaysoo
Succeeded
33370
0a4a8b09 docs(react): update SVGR documentation for Nx 22 The documentation states that SVGR is enabled by default in @nx/webpack and shows the old nx.svgr configuration option for Next.js. As of Nx 22, SVGR is no longer supported out of the box. Documentation should: - Clarify that SVGR requires manual configuration for Webpack, Rspack, and Next.js - Link to official SVGR webpack documentation - Show standard webpack/rspack configuration examples - Show Next.js configuration examples from official docs - Provide withSvgr helper function examples for users using composePlugins with withNx Fixes DOC-326
16 hours ago by jaysoo
Failed
33349
641053e0 fix(testing): use .cts config files for Jest 30+ to fix __dirname issues Jest 30+ uses native type stripping which treats .ts files as ESM by default, causing __dirname to be undefined. Use .cts extension with CommonJS syntax to ensure __dirname is available. Changes: - Detect Jest 30+ and generate .cts files instead of .ts files - Update all generators to use dynamic Jest config file discovery - Update jest configuration targets to reference .cts files - Update SWC configuration to exclude .cts files - Update workspace move/remove generators to handle .cts extension - Add .cts extension to allowed extensions in file processors 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
21 hours ago by jaysoo
Failed
33349
802b8a1c fix(testing): use .cts config files for Jest 30+ to fix __dirname issues Jest 30+ uses native type stripping which treats .ts files as ESM by default, causing __dirname to be undefined. Use .cts extension with CommonJS syntax to ensure __dirname is available. Changes: - Detect Jest 30+ and generate .cts files instead of .ts files - Update all generators to use dynamic Jest config file discovery - Update jest configuration targets to reference .cts files - Update SWC configuration to exclude .cts files - Update workspace move/remove generators to handle .cts extension - Add .cts extension to allowed extensions in file processors 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
21 hours ago by jaysoo
Failed
master
2d78f571 chore(repo): update nx to 22.1.0-beta.4 (#33350) Updating Nx from 22.1.0-beta.3 to 22.1.0-beta.4
1 day ago by jaysoo
Failed
33349
4edcb3f6 fix(testing): use .cts config files for Jest 30+ to fix __dirname issues When using Jest 30+ with Node 22.18+, Jest config files fail with "__dirname is not defined in ES module scope" error. This is because: - Jest 30+ uses Node's native type stripping instead of ts-node - Node 22.18+ has type stripping enabled by default - .ts files are treated as ESM by default where __dirname doesn't exist - Multiple generators hardcode 'jest.config.ts' paths, breaking when files are renamed to .cts For Jest 30+: - Generate jest.config.cts with CommonJS syntax to ensure __dirname is available - All generators dynamically discover Jest config files regardless of extension (.js, .ts, .cjs, .cts, .mjs, .mts) - Config discovery uses findJestConfig() utility function - ensurePackage('@nx/jest') is called before using any @nx/jest utilities - TypeScript excludes all Jest config file extensions For Jest < 30: - Continue using existing jest.config.ts with ESM syntax - Maintain backward compatibility with all existing tests - Modified Jest config generator to detect version and use .cts for Jest 30+ - Created findJestConfig() and findRootJestConfig() utility functions - Updated 15+ generators to use dynamic config discovery: - React application and library generators - Next.js, Remix, React Native, Expo generators - Node and Plugin e2e generators - Workspace move/remove generators - Angular library generator - Fixed ensurePackage ordering to install @nx/jest before requiring its utilities - Updated tsconfig exclude patterns to handle all Jest config extensions - Added comprehensive test coverage for Jest 30 behavior Fixes #32236
2 days ago by jaysoo
Failed
master
a5d34fd9 chore(repo): add .NET format check + codeowners and unify native target handling (#33323) ## Current Behavior Maven and .NET use a bespoke script to handle skipping an optional native target in case a system is not setup on a dev's machine. .NET isn't in codeowners ## Expected Behavior This pull request introduces improvements to the build and formatting workflows for the `.NET` and Maven plugins, streamlining the execution of native targets and updating code ownership assignments. The changes focus on refactoring build scripts to use a unified runner, adding new formatting capabilities for .NET projects, and updating the CODEOWNERS file for clearer team responsibilities. **Build and Format Workflow Improvements** * Refactored the `.NET` analyzer build command in `packages/dotnet/project.json` to use the new `run-native-target.js` script, replacing the previous direct script invocation. [[1]](diffhunk://#diff-036c1a7f2e7d98f5a3207441f2ff1cb25b5b5a03343672ce473f4ff0189a5946L25-R25) [[2]](diffhunk://#diff-42d990ddcbf8d3585553503097ee8b8d1fff8cb6e25e0cd545a87e11d64c03a8L1-L7) * Added new `format-native` and `_format-native` targets to `packages/dotnet/project.json`, enabling verification and fixing of code formatting for the .NET analyzer using `dotnet format`. **Unified Native Target Runner** * Introduced the `scripts/run-native-target.js` script to standardize running native build and install targets, controlled by environment variables for skipping builds. **Maven Plugin Build Refactor** * Updated the Maven plugin's install workflow in `packages/maven/maven-plugin/project.json` to use the new native target runner, and removed the obsolete `scripts/build-maven-analyzer.js` script. [[1]](diffhunk://#diff-2763fe8a7c2989643f53370a14a08c06616e85c29340fd5bcfa1a67d0deaee7aL11-R11) [[2]](diffhunk://#diff-972edab06956ad35145cbc20b8e250e7067fbb288b1f99c92661c24f64d3e69dL1-L7) **Ownership Updates** * Updated the `CODEOWNERS` file to assign `.NET`-related directories to `@FrozenPandaz` and `@AgentEnder`, clarifying team responsibilities. ## Related Issue(s)  Fixes #
2 days ago by jaysoo
Failed
master
a5d34fd9 chore(repo): add .NET format check + codeowners and unify native target handling (#33323) ## Current Behavior Maven and .NET use a bespoke script to handle skipping an optional native target in case a system is not setup on a dev's machine. .NET isn't in codeowners ## Expected Behavior This pull request introduces improvements to the build and formatting workflows for the `.NET` and Maven plugins, streamlining the execution of native targets and updating code ownership assignments. The changes focus on refactoring build scripts to use a unified runner, adding new formatting capabilities for .NET projects, and updating the CODEOWNERS file for clearer team responsibilities. **Build and Format Workflow Improvements** * Refactored the `.NET` analyzer build command in `packages/dotnet/project.json` to use the new `run-native-target.js` script, replacing the previous direct script invocation. [[1]](diffhunk://#diff-036c1a7f2e7d98f5a3207441f2ff1cb25b5b5a03343672ce473f4ff0189a5946L25-R25) [[2]](diffhunk://#diff-42d990ddcbf8d3585553503097ee8b8d1fff8cb6e25e0cd545a87e11d64c03a8L1-L7) * Added new `format-native` and `_format-native` targets to `packages/dotnet/project.json`, enabling verification and fixing of code formatting for the .NET analyzer using `dotnet format`. **Unified Native Target Runner** * Introduced the `scripts/run-native-target.js` script to standardize running native build and install targets, controlled by environment variables for skipping builds. **Maven Plugin Build Refactor** * Updated the Maven plugin's install workflow in `packages/maven/maven-plugin/project.json` to use the new native target runner, and removed the obsolete `scripts/build-maven-analyzer.js` script. [[1]](diffhunk://#diff-2763fe8a7c2989643f53370a14a08c06616e85c29340fd5bcfa1a67d0deaee7aL11-R11) [[2]](diffhunk://#diff-972edab06956ad35145cbc20b8e250e7067fbb288b1f99c92661c24f64d3e69dL1-L7) **Ownership Updates** * Updated the `CODEOWNERS` file to assign `.NET`-related directories to `@FrozenPandaz` and `@AgentEnder`, clarifying team responsibilities. ## Related Issue(s)  Fixes #
3 days ago by jaysoo
Failed
master
4507b5a0 feat(storybook): add support for storybook 10 (#33277) ## Current Behavior We support Storybook 8 and 9 ## Expected Behavior Add support for Storybook 10, bringing Storybook support to 8, 9 and 10 ## Related Issue(s) Fixes #33141
4 days ago by jaysoo
Succeeded
master
b2836639 fix(vite): prevent race-condition when importing @vitejs/plugin-vue (#33307) This PR primes the cache for `@vitejs/plugin-vue`, similar to how we already do for `esbuild`. When `vite.config.ts` is compiled into CJS, then doing `require('@vitejs/plugin-vue')` may error with a race condition if an `import` of the same module is in progress. Fixes #NXC-3289 --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
5 days ago by jaysoo
Succeeded
master
b2836639 fix(vite): prevent race-condition when importing @vitejs/plugin-vue (#33307) This PR primes the cache for `@vitejs/plugin-vue`, similar to how we already do for `esbuild`. When `vite.config.ts` is compiled into CJS, then doing `require('@vitejs/plugin-vue')` may error with a race condition if an `import` of the same module is in progress. Fixes #NXC-3289 --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
5 days ago by jaysoo