Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Failed
master
bfdf892a docs(misc): add info about Okta advanced configuration (#31791) This is to make sure enterprises set the configuration required for our saml integration
43 minutes ago by nartc
Failed
master
2a10953c docs(nx-dev): add CTAs for July 9 webinar (#31769)
1 hour ago by philipjful...
Failed
master
487f8e6d chore(core): replace hardcoded registry URLs with placeholder (#31789) Updated tests to utilize the `customRegistryUrl` variable instead of hardcoded `http://localhost:7190` URLs, improving maintainability and flexibility.
4 hours ago by bcabanes
Failed
master
784a14a5 fix(core): allow any framework value in preset generator schema (#31665) ## Current Behavior When using third-party presets with `npx create-nx-workspace`, passing framework values other than the predefined backend frameworks fails with a schema validation error: ``` Error: Property 'framework' does not match the schema. 'angular' should be one of express,koa,fastify,nest,none. ``` For example: ```bash npx create-nx-workspace --preset=@rig/cli@alpha --framework=angular --theme=pcb --name=hello-world ``` ## Expected Behavior Third-party presets should be able to pass any framework value without schema validation errors, allowing for greater flexibility in the Nx ecosystem. ## Related Issue(s) This fixes the issue where third-party presets cannot pass framework values like 'angular', 'react', 'vue', etc., due to overly restrictive schema validation. ## Changes - Removed the `enum` constraint from the `framework` property in the workspace preset generator schema - The property remains a string type but now accepts any value - Maintains backward compatibility with existing functionality The built-in Nx preset generators still only handle frameworks they know about, but the schema validation no longer blocks third-party presets from passing other framework values. ## Test plan - [x] Workspace package builds successfully - [x] Schema validation allows any string value for framework property - [x] Backward compatibility maintained for existing presets - [ ] Manual test: `npx create-nx-workspace --preset=@rig/cli@alpha --framework=angular` should work without schema validation errors --------- Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: Jason Jean <FrozenPandaz@users.noreply.github.com> Co-authored-by: Claude <claude@anthropic.com>
4 hours ago by FrozenPandaz
Succeeded
master
a73855c7 feat(core): add CI warning for missing remote cache solution (#31678) Running Nx in CI without a remote cache is a common misconfiguration that leads to slow, inefficient builds. This change introduces a proactive warning to prevent this "silent failure" and guide users toward a performant setup. A new `NxCloudCIMessageLifeCycle` hook now checks for a remote cache configuration at the start of any command run within a CI environment. The warning is only displayed if no remote caching is detected. It is intelligently suppressed if the workspace has: * An Nx Cloud access token configured. * A dependency on nx-cloud or @nrwl/nx-cloud. * An on-premise cache provider (s3, gcs, azure, sharedFs) configured in nx.json. * The NX_SELF_HOSTED_REMOTE_CACHE_SERVER environment variable set. * `tasksRunnerOptions` is configured This ensures we only notify users who are genuinely missing out on caching, improving the out-of-the-box developer experience.
4 hours ago by bcabanes
Failed
master
8b3fc7fb fix(core): remove enum constraints from preset generator schema third-party presets can now pass any value for framework, linter, bundler, unitTestRunner, e2eTestRunner, formatter, and packageManager properties without schema validation errors. previously, these properties were restricted to specific enum values, but third-party presets need flexibility to use other tools. fixes issue where npx create-nx-workspace --preset=@rig/cli@alpha --framework=angular would fail with schema validation error.
5 hours ago by FrozenPandaz
Succeeded
master
8b3fc7fb fix(node): reorder addPlugin in normalizeOptions return object (#31785) When creating a node app If you want plugins to be added and `applicationGeneratorInternal` is called instead of `applicationGenerator` the option will be overwritten by the default `false`.
5 hours ago by ndcunningham
Succeeded
master
f8a23eef fix(core): update nx to version 21.3.0-beta.0 (#31771) Update nx repo package version
8 hours ago by ndcunningham
Succeeded
master
f8a23eef fix(core): update nx to version 21.3.0-beta.0 (#31771) Update nx repo package version
9 hours ago by ndcunningham
Failed
master
74302385 fix(core): resolve package.json for @nx/js to improve plugin detection (#31770) This PR updates the package.json inferred target to resolve package.json instead of the entry file.
17 hours ago by jaysoo
Failed
master
74302385 fix(core): resolve package.json for @nx/js to improve plugin detection (#31770) This PR updates the package.json inferred target to resolve package.json instead of the entry file.
2 days ago by jaysoo
Succeeded
master
74302385 fix(core): resolve package.json for @nx/js to improve plugin detection (#31770) This PR updates the package.json inferred target to resolve package.json instead of the entry file.
2 days ago by mandarini
Failed
master
74302385 fix(core): resolve package.json for @nx/js to improve plugin detection (#31770) This PR updates the package.json inferred target to resolve package.json instead of the entry file.
3 days ago by jaysoo
Succeeded
master
74302385 fix(core): resolve package.json for @nx/js to improve plugin detection (#31770) This PR updates the package.json inferred target to resolve package.json instead of the entry file.
3 days ago by JamesHenry
Succeeded
master
74302385 fix(core): resolve package.json for @nx/js to improve plugin detection (#31770) This PR updates the package.json inferred target to resolve package.json instead of the entry file.
3 days ago by ndcunningham
Succeeded
master
ad14f2f4 chore(repo): update e2e nightly report adding more golden test and updating the report (#31752) This PR changes our Nightly GHA status reporting from a per-project-per-environment basis to a per-project basis. This consolidation will make the status reports easier to understand by reducing the granularity of reporting. Additionally, we now capture timed-out jobs as a failure instead of being overlooked. Sample: ``` Golden Test Failure ⭐ : Golden Projects ✅ : Passing: 15 ❌ : Failing: 1 🚨 : Failed Golden Projects | Failed project | |--------------------------------| | e2e-node | ```
3 days ago by ndcunningham
Failed
master
9d5030b2 fix(js): improve typescript plugin build detection (#31533) This PR enhances the typescript plugin build detection. Notably the changes include: - Add absolute path handling for package.json entry points. - Simplify the buildable verification - Add glob pattern matching for `include` patterns. MISC: - Also fixes `e2e-rollup` test failing due to the typescript plugin having the same build target as rollup so it created an unexpected output. closes: #29670
3 days ago by ndcunningham
Succeeded
master
9d5030b2 fix(js): improve typescript plugin build detection (#31533) This PR enhances the typescript plugin build detection. Notably the changes include: - Add absolute path handling for package.json entry points. - Simplify the buildable verification - Add glob pattern matching for `include` patterns. MISC: - Also fixes `e2e-rollup` test failing due to the typescript plugin having the same build target as rollup so it created an unexpected output. closes: #29670
3 days ago by AgentEnder
Succeeded
master
9d5030b2 fix(js): improve typescript plugin build detection (#31533) This PR enhances the typescript plugin build detection. Notably the changes include: - Add absolute path handling for package.json entry points. - Simplify the buildable verification - Add glob pattern matching for `include` patterns. MISC: - Also fixes `e2e-rollup` test failing due to the typescript plugin having the same build target as rollup so it created an unexpected output. closes: #29670
3 days ago by ndcunningham
Failed
master
47e1a9ce fix(storybook): handle hyphenated framework names in pnpm dependency installation (#31760) ## Current Behavior When installing Storybook dependencies with pnpm, the regex for extracting base framework names from compound framework packages (e.g., @storybook/web-components-vite) was not properly handling hyphens in framework names. This caused it to extract incorrect base framework names like @storybook/web instead of @storybook/web-components, leading to attempts to install non-existent packages. ## Expected Behavior The regex should properly extract base framework names that include hyphens, correctly identifying @storybook/web-components as the base framework for packages like @storybook/web-components-vite. This ensures that only valid Storybook packages are installed during dependency resolution. ## Related Issue(s) Fixes #31292
3 days ago by Coly010