Nx
Enterprise
Nx
Sign in / Sign up
Open main menu
Nx
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
22.6.x
8bd4c182 fix(maven): use require for tree-kill to avoid esModuleInterop mismatch between lib and spec configs
by Jason Jean
J
Failed
22.6.x
c9d51d31 fix(core): update cleanup mock to match async signature in package-json spec
by Jason Jean
J
Failed
22.6.x
591ce2e7 chore(repo): update lockfile
by Jason Jean
J
Failed
22.6.x
87180326 chore(repo): fix gradle lint failure
by Jason Jean
J
Canceled
22.6.x
c65495b4 Revert "fix(linter): infer extended tsconfig files as task inputs (#35190)" This reverts commit 00c69719f5b463a8b57003b8cc10c1529843b8aa.
by Jason Jean
J
Failed
22.6.x
6a32696e feat(core): prompt for setup mode when running nx init in empty git directory (#35226) ## Current Behavior When running `nx init` in an empty git directory (no `package.json`), the V2 init handler silently defaults to the `.nx` installation method without prompting the user. This may not be suitable for users who intend to create a JavaScript/TypeScript project and would prefer a `package.json`-based setup. ## Expected Behavior When running `nx init` in an empty git directory, users are now prompted to choose between two setup methods: - **`.nx installation`** — recommended for non-JavaScript projects (Gradle, .NET, etc.) - **`package.json installation`** — recommended for JavaScript/TypeScript projects The prompt only appears when: - No `package.json` exists in the directory - The `--useDotNxInstallation` flag was not explicitly passed - Running in interactive mode (not AI agent mode) If the user chooses `package.json`, a minimal `package.json` is created and the existing npm-repo setup flow takes over. If they choose `.nx`, the existing dot-nx setup flow is used. In both cases, the workspace is created in the current directory (not a subfolder). ## Related Issue(s) Fixes NXC-3983 (cherry picked from commit ea644b3e49f332a09db8bcb0afea253249922a48)
by Craigory C...
C
Canceled
22.6.x
ad59aab5 chore(repo): fix nx build
by FrozenPandaz
F
Canceled
22.6.x
c9bcccb2 Revert "fix(core): kill discrete tasks and use tree-kill for batch cleanup on SIGINT (#35175)" This reverts commit d0f8012c74017b8954c9326af621f340d58d3863.
by Jack Hsu
J
Failed
22.6.x
6e96dab7 fix(misc): bump axios to 1.15.0 for all packages (#35237) Closes #NXC-4237
by Jack Hsu
J
Failed
22.6.x
2fa235d1 docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com> (cherry picked from commit 5a7e851ce1c8c1a22eb1a57621c4814ae141b266)
by Juri Strum...
J
Failed
22.6.x
44abcb2a fix(js): use explicit nx/bin/nx path in start-local-registry (#35127) ## Current Behavior `start-local-registry.ts` uses `require.resolve('nx')` to find the nx CLI binary for forking a child process. This resolves the package's `main` entry point, which only incidentally points to the binary. In pnpm strict mode, this resolution fails when called from within `@nx/js` because `@nx/js` doesn't declare `nx` as a direct dependency. ## Expected Behavior Use `require.resolve('nx/bin/nx')` to explicitly resolve the CLI binary entry point. This is semantically correct (the intent is to fork the nx CLI) and doesn't rely on the `main` field or pnpm hoisting behavior. (cherry picked from commit 49a0e3f69edca0c720fcac1661c05f952289c6ff)
by Jack Hsu
J
Failed
22.6.x
b013f93d fix(repo): disable ts-jest diagnostics for workspace-plugin tests
by FrozenPandaz
F
Canceled
22.6.x
620949f3 chore(repo): fix lockfile
by FrozenPandaz
F
Failed
22.6.x
5771eb33 fix(react-native): use vite's transformWithEsbuild instead of direct esbuild import The react-native vite config template imported esbuild directly, which fails during project graph processing in pnpm strict mode because esbuild is only a transitive dependency of vite and not hoisted to root node_modules. Fixes e2e-detox:e2e-macos-local failure.
by Colum Ferry
C
Failed
22.6.x
070ca28d fix(core): no-interactive should disable prompts during migrate (#35106) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Craigory C...
C
Failed
22.6.x
070ca28d fix(core): no-interactive should disable prompts during migrate (#35106) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Craigory C...
C
Canceled
22.6.x
d95503af chore(repo): fix workspace plugin
by FrozenPandaz
F
Failed
22.6.x
d95503af chore(repo): fix workspace plugin
by FrozenPandaz
F
Failed
22.6.x
b070e234 fix(repo): fix lockfile
by FrozenPandaz
F
Succeeded
22.6.x
017751bc fix(misc): handle non-interactive mode and add template shorthand names for CNW (#35045) This PR address some common errors seen during CNW around `--template` and `--preset` during non-interactive flows that are not AI agents. Also sees that some template names are not qualified with `nrwl/<name>-template` so we can normal though (which also makes it shorter in docs). ## Current Behavior In non-interactive contexts (IDE terminals, scripts, SSH without `-t`), `determineTemplate()` returns `'custom'` which routes to the preset flow. Without `--preset` provided, this throws "Preset is required", which affects ~15 users/day (~145 occurrences Mar 18-27). Users must also pass full template paths like `--template=nrwl/angular-template`. ## Expected Behavior Non-interactive mode defaults to `nrwl/empty-template` (template flow) instead of `'custom'` (preset flow) when neither `--preset` nor `--template` is provided. Shorthand template names are supported: - `--template=angular` → `nrwl/angular-template` - `--template=react` → `nrwl/react-template` - `--template=typescript` → `nrwl/typescript-template` - `--template=empty` → `nrwl/empty-template` ## Related Issue(s) Fixes NXC-4153
by Jack Hsu
J
Previous page
Previous
Next
Next page