Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
21.2.0
18155f45 docs(nx-cloud): update release notes (#31563)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
9 days ago by FrozenPandaz
Succeeded
21.2.0
18155f45 docs(nx-cloud): update release notes (#31563)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
9 days ago by FrozenPandaz
Succeeded
21.2.0-beta.5
df4f1363 fix(core): scope native logging to nx module by default (#31530) ## Current Behavior The native logging is currently set to a global 'info' level, which can produce verbose output that may not be relevant to users. ## Expected Behavior Native logging should be scoped to the 'nx::native' module by default with 'info' level, reducing noise while still allowing users to control logging verbosity through the `NX_NATIVE_LOGGING` environment variable. ## Related Issue(s) This improves the developer experience by providing more focused logging output and reduces unnecessary verbosity in the console. Fixes https://github.com/nrwl/nx/issues/31518
11 days ago by FrozenPandaz
Succeeded
21.2.0-beta.4
c8ff3394 fix(core): remove log_error function and standardize logging (#31515) ## Current Behavior The codebase has separate `logError` and `logDebug` functions in the native logging infrastructure, with both error and debug logging paths. ## Expected Behavior Consolidate logging to use a single standardized approach. Error messages are now logged through the debug channel for consistency. ## Related Issue(s) This change standardizes the logging interface by removing the separate error logging function and routing all log messages through the debug logger.
12 days ago by FrozenPandaz
Succeeded
21.2.0-beta.3
02278920 chore(repo): fix publish workflow (#31510) ## Current Behavior The publish workflow was failing because the preinstall script was exiting with code 1 when detecting an older Node.js version, causing the entire publishing process to fail. ## Expected Behavior The preinstall script should warn about Node.js version requirements but not exit with an error code during publishing, allowing the workflow to continue. ## Related Issue(s) This fixes a critical issue preventing package publishing due to Node.js version check failures in CI environments. The fix changes: - `console.error()` to `console.warn()` for better log categorization - Removes `process.exit(1)` to prevent workflow termination - Adds the actual Node.js version to the warning message for better debugging This ensures the publish workflow can complete successfully while still providing visibility into Node.js version mismatches.
12 days ago by FrozenPandaz
Succeeded
21.2.0-beta.3
35f54044 fix(core): default to 'run' target when only project is specified (#31452) ## Current Behavior When running `nx run <project>` without specifying a target, the command always fails with an error message "Both project and target have to be specified", even if the project has a "run" target defined. ## Expected Behavior When running `nx run <project>` without specifying a target, the command should check if the project has a "run" target defined. If it does, use it as the default target. This improves developer experience by allowing simpler commands like `nx run myapp` instead of `nx run myapp:run`. ## Related Issue(s) This change improves the developer experience for projects that have a "run" target defined, making the CLI more intuitive. ## Changes Made - Modified `packages/nx/src/command-line/run/run-one.ts` to check for a "run" target when no target is specified - Added comprehensive test coverage in `e2e/nx/src/run.test.ts` to verify: - Projects with a "run" target default to it when no target is specified - Projects without a "run" target still show the original error message - Maintains full backward compatibility ## Testing - All existing tests pass - Added new e2e tests to verify the behavior - Ran full validation suite (`nx prepush`) successfully
13 days ago by FrozenPandaz
Failed
21.2.0-beta.3
8941362d fix(core): scope typescript resolution cache correctly when processing the graph (#31455) ## Current Behavior When using Node.js subpath imports with the same name in different projects, the Nx graph incorrectly picks up seemingly random dependencies between projects that shouldn't exist. This happens because the result of the resolution performed with TypeScript is cached using the import path as the cache key. The problem with that is that multiple projects can have the same subpath import name pointing to internal files of the project, so when the resolution is made for the first project (say `project1`), the result will be cached and incorrectly reused for other projects with the same subpath import name. So, all projects with the same subpath import name would resolve the dependency to the first project (`project1`). The same could happen to projects with TS path mappings defined in the project's tsconfig file. These TS path mappings would only apply to the project internally and therefore, other unrelated projects could also define them with the same name pointing to different files. ## Expected Behavior The Node.js subpath imports should be handled correctly. The TypeScript resolution result should be cached safely and scoped to the project from which the import is being done. ## Related Issue(s) Fixes #31223
15 days ago by FrozenPandaz
Succeeded
21.2.0-beta.2
2f8eb245 docs(core): add docs for tui options in nx.json (#31459) This PR adds the missing `tui` property in `nx.json` on this page: https://nx.dev/reference/nx-json <img width="884" alt="Screenshot 2025-06-04 at 1 10 04 PM" src="https://github.com/user-attachments/assets/d7edb8dd-7b1a-4e3e-a738-4eb0dbb1feba" /> Preview: https://nx-dev-git-docs-add-tui-option-nrwl.vercel.app/reference/nx-json
17 days ago by FrozenPandaz
Succeeded
21.2.0-beta.1
752d418f feat(angular): support angular cli v20.0.0-rc.3 (#30715) Add support for the Angular CLI **20.0.0-rc.3** version.
27 days ago by jaysoo