Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
master
d5de2c6a fix(testing): support NX_CACHE_PROJECT_GRAPH when reading inferred config from jest cache file (#32380) ## Current Behavior The Jest plugin does not use `NX_CACHE_PROJECT_GRAPH` in its implementation. Unlike other plugins (e.g., ESLint, TypeScript), it does not provide a way to control or disable its internal caching behavior. ## Expected Behavior The Jest plugin should leverage `NX_CACHE_PROJECT_GRAPH`, ensuring consistent caching behavior across Nx plugins. This would make it easier to manage or override caching strategies when building higher-order plugins that extend Nx core functionality. ## Related Issue(s) Fixes # --- ### Additional Context * When creating higher-order plugins that extend Nx core plugins, it’s often useful to manage cache differently. Without this, concurrency issues can occur if `createNodesV2` is invoked multiple times in parallel. * This highlights a broader need for improved plugin extensibility: * Instead of re-invoking `createNodesV2` (which handles multiple files, cache, etc.), it would be helpful to expose lower-level functions responsible only for generating configuration. * This would give plugin authors more granular control while reducing unintended side effects.
4 hours ago by jogelin
Failed
master
d5de2c6a fix(testing): support NX_CACHE_PROJECT_GRAPH when reading inferred config from jest cache file (#32380) ## Current Behavior The Jest plugin does not use `NX_CACHE_PROJECT_GRAPH` in its implementation. Unlike other plugins (e.g., ESLint, TypeScript), it does not provide a way to control or disable its internal caching behavior. ## Expected Behavior The Jest plugin should leverage `NX_CACHE_PROJECT_GRAPH`, ensuring consistent caching behavior across Nx plugins. This would make it easier to manage or override caching strategies when building higher-order plugins that extend Nx core functionality. ## Related Issue(s) Fixes # --- ### Additional Context * When creating higher-order plugins that extend Nx core plugins, it’s often useful to manage cache differently. Without this, concurrency issues can occur if `createNodesV2` is invoked multiple times in parallel. * This highlights a broader need for improved plugin extensibility: * Instead of re-invoking `createNodesV2` (which handles multiple files, cache, etc.), it would be helpful to expose lower-level functions responsible only for generating configuration. * This would give plugin authors more granular control while reducing unintended side effects.
4 hours ago by jogelin
Succeeded
master
d5de2c6a fix(testing): support NX_CACHE_PROJECT_GRAPH when reading inferred config from jest cache file (#32380) ## Current Behavior The Jest plugin does not use `NX_CACHE_PROJECT_GRAPH` in its implementation. Unlike other plugins (e.g., ESLint, TypeScript), it does not provide a way to control or disable its internal caching behavior. ## Expected Behavior The Jest plugin should leverage `NX_CACHE_PROJECT_GRAPH`, ensuring consistent caching behavior across Nx plugins. This would make it easier to manage or override caching strategies when building higher-order plugins that extend Nx core functionality. ## Related Issue(s) Fixes # --- ### Additional Context * When creating higher-order plugins that extend Nx core plugins, it’s often useful to manage cache differently. Without this, concurrency issues can occur if `createNodesV2` is invoked multiple times in parallel. * This highlights a broader need for improved plugin extensibility: * Instead of re-invoking `createNodesV2` (which handles multiple files, cache, etc.), it would be helpful to expose lower-level functions responsible only for generating configuration. * This would give plugin authors more granular control while reducing unintended side effects.
5 hours ago by jogelin
Succeeded
master
d5de2c6a fix(testing): support NX_CACHE_PROJECT_GRAPH when reading inferred config from jest cache file (#32380) ## Current Behavior The Jest plugin does not use `NX_CACHE_PROJECT_GRAPH` in its implementation. Unlike other plugins (e.g., ESLint, TypeScript), it does not provide a way to control or disable its internal caching behavior. ## Expected Behavior The Jest plugin should leverage `NX_CACHE_PROJECT_GRAPH`, ensuring consistent caching behavior across Nx plugins. This would make it easier to manage or override caching strategies when building higher-order plugins that extend Nx core functionality. ## Related Issue(s) Fixes # --- ### Additional Context * When creating higher-order plugins that extend Nx core plugins, it’s often useful to manage cache differently. Without this, concurrency issues can occur if `createNodesV2` is invoked multiple times in parallel. * This highlights a broader need for improved plugin extensibility: * Instead of re-invoking `createNodesV2` (which handles multiple files, cache, etc.), it would be helpful to expose lower-level functions responsible only for generating configuration. * This would give plugin authors more granular control while reducing unintended side effects.
6 hours ago by jogelin
Succeeded
master
d5de2c6a fix(testing): support NX_CACHE_PROJECT_GRAPH when reading inferred config from jest cache file (#32380) ## Current Behavior The Jest plugin does not use `NX_CACHE_PROJECT_GRAPH` in its implementation. Unlike other plugins (e.g., ESLint, TypeScript), it does not provide a way to control or disable its internal caching behavior. ## Expected Behavior The Jest plugin should leverage `NX_CACHE_PROJECT_GRAPH`, ensuring consistent caching behavior across Nx plugins. This would make it easier to manage or override caching strategies when building higher-order plugins that extend Nx core functionality. ## Related Issue(s) Fixes # --- ### Additional Context * When creating higher-order plugins that extend Nx core plugins, it’s often useful to manage cache differently. Without this, concurrency issues can occur if `createNodesV2` is invoked multiple times in parallel. * This highlights a broader need for improved plugin extensibility: * Instead of re-invoking `createNodesV2` (which handles multiple files, cache, etc.), it would be helpful to expose lower-level functions responsible only for generating configuration. * This would give plugin authors more granular control while reducing unintended side effects.
6 hours ago by jogelin
Succeeded
32380
b6859769 fix(testing): support NX_CACHE_PROJECT_GRAPH when reading inferred config from jest cache file
8 hours ago by jogelin
Failed
master
31661c83 fix(plugin): fix e2e-project generator when the e2e target is inferred (#31809)
1 month ago by jogelin
Succeeded
31809
a206900e fix(nx-plugin): fix e2e-project generator when the e2e target is covered by configured plugin
2 months ago by jogelin
Failed
31809
1f639aed fix(plugin): fix e2e-project generator when the e2e target is covered by configured plugin
2 months ago by jogelin
Succeeded
master
fd31fa63 fix(js): resolve asset paths relative to workspace root instead of cwd (#31664) ## Description This PR fixes an issue where asset files copied during a build using the `@nx/js:tsc` executor are placed in the wrong directory depending on the current working directory from which the `nx` command is executed. This behavior becomes particularly problematic in scenarios like release workflows that rely on `preVersionCommand` to run E2E tests. For instance, when using tools like Jest from the root of an E2E project, scripts like `start-local-registry` may trigger a build and run the `preVersionCommand`. However, instead of placing assets in the expected `dist` folder of the project, they are incorrectly copied relative to the E2E folder’s location. ## Reproduction Steps 1. Create a new Nx workspace: ```bash npx --yes create-nx-workspace assets-issue --preset=ts --no-interactive cd assets-issue ``` 2. Add the Nx Plugin package: ```bash nx add @nx/plugin ``` 3. Generate a new plugin: ```bash nx g @nx/plugin:plugin packages/my-plugin --linter eslint --unitTestRunner jest ``` 4. Add a generator to the plugin: ```bash nx g @nx/plugin:generator packages/my-plugin/src/generators/my-generator ``` 5. Build the plugin from the workspace root: ```bash nx build my-plugin ``` ✅ Assets are copied correctly: ``` dist/packages/my-plugin/generators/files/src/index.ts.template dist/packages/my-plugin/generators/schema.json dist/packages/my-plugin/generators/schema.d.ts ``` 6. Now build the same project from a nested folder: ```bash mkdir e2e && cd e2e nx build my-plugin --skip-nx-cache ``` ❌ Assets are copied relative to the current folder: ``` e2e/packages/my-plugin/dist/generators/files/src/index.ts.template e2e/packages/my-plugin/dist/generators/schema.json e2e/packages/my-plugin/dist/generators/schema.d.ts ``` ## Expected Behavior The build output—especially copied assets—should always respect the project’s `outputPath` configuration regardless of where the `nx` command is invoked from. The behavior should be consistent and **not influenced by `process.cwd()`**.
2 months ago by jogelin
Succeeded
31664
acb2d450 fix(js): resolve asset paths relative to workspace root instead of cwd Assets were incorrectly copied when running nx build from nested directories because path.relative() resolved relative outputDir against process.cwd() instead of the workspace root. Fixes both string assets ('LICENSE') and asset globs with relative outputDir by ensuring paths are always resolved relative to opts.rootDir.
2 months ago by jogelin
Failed
31664
431a6258 ix(js): resolve asset paths relative to workspace root instead of cwd Assets were incorrectly copied when running nx build from nested directories because path.relative() resolved relative outputDir against process.cwd() instead of the workspace root. Fixes both string assets ('LICENSE') and asset globs with relative outputDir by ensuring paths are always resolved relative to opts.rootDir.
2 months ago by jogelin
Succeeded
master
57840586 feat(js): support publishing with registryConfigKey when pnpm >=9.15.7 <10.0.0 || >=10.5.0 (#31622)
2 months ago by jogelin
Succeeded
31622
cb880339 feat(js): support publishing with registryConfigKey when pnpm > 9.15.7
2 months ago by jogelin
Canceled
31622
a0fb16d1 feat(js): support publishing with registryConfigKey when pnpm > 9.15.7
2 months ago by jogelin
Canceled
31622
4ccc5489 feat(js): support publishing with registryConfigKey when pnpm > 9.15.7
2 months ago by jogelin
Canceled
31622
70be5c7d feat(js): support publishing with registryConfigKey when pnpm > 9.15.7
2 months ago by jogelin
Succeeded
31622
5142322c feat(js): support publishing with registryConfigKey when pnpm > 9.15.7
2 months ago by jogelin
Canceled
31622
00552c88 feat(js): support publishing with registryConfigKey when pnpm > 9.15.7
2 months ago by jogelin
Succeeded
31622
ddc9c97b feat(js): support publishing with registryConfigKey when pnpm > 9.15.7
2 months ago by jogelin