Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Succeeded
master
c888ac72 fix(maven): remove incorrect threadSafe to parallelism mapping (#33678) ## Current Behavior The Maven plugin incorrectly maps Maven's `isThreadSafe` mojo property to Nx's `parallelism` target property. Maven's `isThreadSafe` indicates whether a mojo can safely run in parallel with other mojos of the same type within the same Maven build (multi-threaded Maven builds). ## Expected Behavior Nx's `parallelism` controls whether the target can run in parallel alongside anything else - a fundamentally different concept. All Maven targets now default to `parallelism: true`, letting Nx handle parallelism based on its own task graph analysis rather than using Maven's unrelated thread-safety concept. ## Related Issue(s) N/A - Internal cleanup based on code review feedback.
2 hours ago by FrozenPandaz
Succeeded
359
68e34d49 feat(schematics): use @ngrx/schematics * ngrx collection now extends @ngrx/schematics * modify the nrwl `ngrx` schematic to use `@ngrx/schematics` to generate the initial source for actions, reducers, and effects * modify the generated source to conform to Nx standards * generate init and interface files * remove template files for action, effect, and reducer scaffolding * modify collection to extend `@ngrx/schematics` so the ngrx commands are also easily accessible * inject dataloaded enums into action class * configure nx workspace devDep on @ngrx/schematics version * override ngrx effects.spec.ts with nx templated version fixes #174.
2 hours ago by ThomasBurl...
Succeeded
master
c888ac72 fix(maven): remove incorrect threadSafe to parallelism mapping (#33678) ## Current Behavior The Maven plugin incorrectly maps Maven's `isThreadSafe` mojo property to Nx's `parallelism` target property. Maven's `isThreadSafe` indicates whether a mojo can safely run in parallel with other mojos of the same type within the same Maven build (multi-threaded Maven builds). ## Expected Behavior Nx's `parallelism` controls whether the target can run in parallel alongside anything else - a fundamentally different concept. All Maven targets now default to `parallelism: true`, letting Nx handle parallelism based on its own task graph analysis rather than using Maven's unrelated thread-safety concept. ## Related Issue(s) N/A - Internal cleanup based on code review feedback.
2 hours ago by FrozenPandaz
Succeeded
master
c888ac72 fix(maven): remove incorrect threadSafe to parallelism mapping (#33678) ## Current Behavior The Maven plugin incorrectly maps Maven's `isThreadSafe` mojo property to Nx's `parallelism` target property. Maven's `isThreadSafe` indicates whether a mojo can safely run in parallel with other mojos of the same type within the same Maven build (multi-threaded Maven builds). ## Expected Behavior Nx's `parallelism` controls whether the target can run in parallel alongside anything else - a fundamentally different concept. All Maven targets now default to `parallelism: true`, letting Nx handle parallelism based on its own task graph analysis rather than using Maven's unrelated thread-safety concept. ## Related Issue(s) N/A - Internal cleanup based on code review feedback.
2 hours ago by FrozenPandaz
Succeeded
348
e8d85523 feat(nx): tell users to upgrade schematics and also update nx
2 hours ago by FrozenPandaz
Succeeded
master
731aba37 fix(testing): remove --no-experimental-strip-types flag from @nx/jest/plugin + migrate to jest.config.cts if needed (#33657) ## Current Behavior On Node.js v24+, the `@nx/jest/plugin` sets `--no-experimental-strip-types` in NODE_OPTIONS which causes an error: "node: --no-experimental-strip-types is not allowed in NODE_OPTIONS". Additionally, `jest.config.ts` files using ESM syntax (`export default`, `import`) fail to load correctly under Node.js type-stripping when the project is configured for CommonJS. ## Expected Behavior - Remove the NODE_OPTIONS manipulation that adds `--no-experimental-strip-types` - Add a migration (22.2.0-beta.2) that converts `jest.config.ts` files from ESM to CJS syntax for projects using `@nx/jest/plugin` - The migration only runs when `@nx/jest/plugin` is registered in `nx.json` - Projects with `type: module` are warned as they're incompatible with the plugin - Files using ESM-only features (import.meta, top-level await) are skipped with a warning for manual conversion ## Demo https://www.loom.com/share/8a157a0b01d144ae8d6ae48b9b0cd0e4 ## Related Issue(s) Closes NXC-3541 --------- Co-authored-by: Claude <noreply@anthropic.com>
2 hours ago by jaysoo
Succeeded
389
d0d3950f feat(schematics): add ability to create bazel workspace
2 hours ago by FrozenPandaz
Succeeded
master
c888ac72 fix(maven): remove incorrect threadSafe to parallelism mapping (#33678) ## Current Behavior The Maven plugin incorrectly maps Maven's `isThreadSafe` mojo property to Nx's `parallelism` target property. Maven's `isThreadSafe` indicates whether a mojo can safely run in parallel with other mojos of the same type within the same Maven build (multi-threaded Maven builds). ## Expected Behavior Nx's `parallelism` controls whether the target can run in parallel alongside anything else - a fundamentally different concept. All Maven targets now default to `parallelism: true`, letting Nx handle parallelism based on its own task graph analysis rather than using Maven's unrelated thread-safety concept. ## Related Issue(s) N/A - Internal cleanup based on code review feedback.
3 hours ago by FrozenPandaz
Succeeded
33678
8dd7ae25 fix(maven): remove incorrect threadSafe to parallelism mapping Maven's isThreadSafe indicates whether a mojo can safely run in parallel with other mojos within the same Maven build. This is not equivalent to Nx's parallelism, which controls whether multiple instances of the same target can run in parallel across different projects. All targets now default to parallelism: true, letting Nx handle parallelism based on its own task graph analysis.
4 hours ago by FrozenPandaz
Canceled
33678
2faba544 fix(maven): remove incorrect threadSafe to parallelism mapping Maven's isThreadSafe indicates whether a mojo can safely run in parallel with other mojos within the same Maven build. This is not equivalent to Nx's parallelism, which controls whether multiple instances of the same target can run in parallel across different projects. All targets now default to parallelism: true, letting Nx handle parallelism based on its own task graph analysis.
4 hours ago by FrozenPandaz
Succeeded
master
731aba37 fix(testing): remove --no-experimental-strip-types flag from @nx/jest/plugin + migrate to jest.config.cts if needed (#33657) ## Current Behavior On Node.js v24+, the `@nx/jest/plugin` sets `--no-experimental-strip-types` in NODE_OPTIONS which causes an error: "node: --no-experimental-strip-types is not allowed in NODE_OPTIONS". Additionally, `jest.config.ts` files using ESM syntax (`export default`, `import`) fail to load correctly under Node.js type-stripping when the project is configured for CommonJS. ## Expected Behavior - Remove the NODE_OPTIONS manipulation that adds `--no-experimental-strip-types` - Add a migration (22.2.0-beta.2) that converts `jest.config.ts` files from ESM to CJS syntax for projects using `@nx/jest/plugin` - The migration only runs when `@nx/jest/plugin` is registered in `nx.json` - Projects with `type: module` are warned as they're incompatible with the plugin - Files using ESM-only features (import.meta, top-level await) are skipped with a warning for manual conversion ## Demo https://www.loom.com/share/8a157a0b01d144ae8d6ae48b9b0cd0e4 ## Related Issue(s) Closes NXC-3541 --------- Co-authored-by: Claude <noreply@anthropic.com>
4 hours ago by jaysoo
Succeeded
993
2e1aad22 enhancement(schematics): improve perf of affected Ensure getProjectNodes is called once per command
4 hours ago by FrozenPandaz
Succeeded
33677
ab611fa4 feat(misc): add Framer rewrite support for nx-dev ## Current Behavior The nx-dev Next.js app can only serve pages from its own codebase or proxy to Astro docs. ## Expected Behavior Support proxying specific pages to a Framer site via environment variables: - `NEXT_PUBLIC_FRAMER_URL`: Base URL of the Framer site - `NEXT_PUBLIC_FRAMER_REWRITES`: Comma-separated paths for new pages For existing pages like `/ai`, the proxy is handled in `getServerSideProps`. ## Related Issue(s) Fixes DOC-349 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
5 hours ago by jaysoo
Succeeded
33676
6ff9662f chore(repo): clean up migrations.json after migration
6 hours ago by FrozenPandaz
Succeeded
master
731aba37 fix(testing): remove --no-experimental-strip-types flag from @nx/jest/plugin + migrate to jest.config.cts if needed (#33657) ## Current Behavior On Node.js v24+, the `@nx/jest/plugin` sets `--no-experimental-strip-types` in NODE_OPTIONS which causes an error: "node: --no-experimental-strip-types is not allowed in NODE_OPTIONS". Additionally, `jest.config.ts` files using ESM syntax (`export default`, `import`) fail to load correctly under Node.js type-stripping when the project is configured for CommonJS. ## Expected Behavior - Remove the NODE_OPTIONS manipulation that adds `--no-experimental-strip-types` - Add a migration (22.2.0-beta.2) that converts `jest.config.ts` files from ESM to CJS syntax for projects using `@nx/jest/plugin` - The migration only runs when `@nx/jest/plugin` is registered in `nx.json` - Projects with `type: module` are warned as they're incompatible with the plugin - Files using ESM-only features (import.meta, top-level await) are skipped with a warning for manual conversion ## Demo https://www.loom.com/share/8a157a0b01d144ae8d6ae48b9b0cd0e4 ## Related Issue(s) Closes NXC-3541 --------- Co-authored-by: Claude <noreply@anthropic.com>
6 hours ago by AgentEnder
Succeeded
33675
19ffc859 feat(repo): enable wayland-data-control feature for arboard
6 hours ago by FrozenPandaz
Failed
33673
Fix Ready
9e19ff9a fix(core): update packages/nx/src/native/pseudo_terminal/pseudo_terminal.rs Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
6 hours ago by AgentEnder
Canceled
33673
75d7b8dc fix(core): prevent duplicate output of tasks in tui
7 hours ago by AgentEnder
Succeeded
master
731aba37 fix(testing): remove --no-experimental-strip-types flag from @nx/jest/plugin + migrate to jest.config.cts if needed (#33657) ## Current Behavior On Node.js v24+, the `@nx/jest/plugin` sets `--no-experimental-strip-types` in NODE_OPTIONS which causes an error: "node: --no-experimental-strip-types is not allowed in NODE_OPTIONS". Additionally, `jest.config.ts` files using ESM syntax (`export default`, `import`) fail to load correctly under Node.js type-stripping when the project is configured for CommonJS. ## Expected Behavior - Remove the NODE_OPTIONS manipulation that adds `--no-experimental-strip-types` - Add a migration (22.2.0-beta.2) that converts `jest.config.ts` files from ESM to CJS syntax for projects using `@nx/jest/plugin` - The migration only runs when `@nx/jest/plugin` is registered in `nx.json` - Projects with `type: module` are warned as they're incompatible with the plugin - Files using ESM-only features (import.meta, top-level await) are skipped with a warning for manual conversion ## Demo https://www.loom.com/share/8a157a0b01d144ae8d6ae48b9b0cd0e4 ## Related Issue(s) Closes NXC-3541 --------- Co-authored-by: Claude <noreply@anthropic.com>
7 hours ago by jaysoo
Succeeded
358
57a1e6e1
8 hours ago
u