chore: use @nx/graph for graph implementation details

docs(webpack): update NxAppWebpackPlugin reference (#27156 )
## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
2024-07-27 22:56:21 +04:00 · 2024-07-26 17:02:35 +01:00 · 2024-07-26 16:59:20 +01:00 · 2024-07-26 11:54:09 -04:00 · 2024-07-26 11:40:39 -04:00 · 2024-07-26 08:03:00 -07:00
2126 changed files with 127233 additions and 39312 deletions
@@ -86,6 +86,7 @@ jobs:
      NX_E2E_RUN_E2E: 'true'
      NX_CI_EXECUTION_ENV: 'linux'
      NX_CLOUD_DTE_V2: 'true'
+      NX_CLOUD_DTE_SUMMARY: 'true'
    steps:
      - checkout
      - nx/set-shas:
@@ -94,7 +95,7 @@ jobs:
      - run:
          command: |
            sudo apt-get update
-            sudo apt-get install -y ca-certificates lsof
+            sudo apt-get install -y ca-certificates lsof libvips-dev libglib2.0-dev libgirepository1.0-dev
      - browser-tools/install-chrome
      - run-pnpm-install:
          os: linux
@@ -114,8 +115,7 @@ jobs:
            pnpm nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte &
            pids+=($!)

-            (pnpm nx affected --targets=lint,test,build --base=$NX_BASE --head=$NX_HEAD --parallel=3 &&
-            pnpm nx affected --targets=e2e,e2e-ci --base=$NX_BASE --head=$NX_HEAD --parallel=1) &
+            pnpm nx affected --targets=lint,test,build,e2e,e2e-ci --base=$NX_BASE --head=$NX_HEAD --parallel=3 &
            pids+=($!)

            for pid in "${pids[@]}"; do
@@ -158,7 +158,12 @@ jobs:
      - run:
          name: Run E2E Tests for macOS
          command: |
-            pnpm nx affected -t e2e-macos-ci --parallel=1 --base=$NX_BASE --head=$NX_HEAD
+            HAS_CHANGED=$(node ./scripts/check-react-native-changes.js $NX_BASE $NX_HEAD);
+            if $HAS_CHANGED; then
+              pnpm nx affected -t e2e-macos-ci --parallel=1 --base=$NX_BASE --head=$NX_HEAD
+            else
+              echo "Skip E2E tests for macOS as there are no changes in React Native projects."
+            fi
          no_output_timeout: 45m

 # -------------------------
@@ -0,0 +1,7 @@
+FROM mcr.microsoft.com/devcontainers/typescript-node:20-bullseye
+
+# Update the underlying (Debian) OS, to make sure we have the latest security patches and libraries like 'GLIBC' 
+RUN sudo apt-get update  && sudo apt-get -y upgrade
+
+# Update pnpm
+RUN npm install -g pnpm@8.15.7
@@ -3,7 +3,10 @@
 {
  "name": "NxDevContainer",
  // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
-  "image": "mcr.microsoft.com/devcontainers/typescript-node:20-bullseye",
+  "build": {
+    // Path is relative to the devcontainer.json file.
+    "dockerfile": "Dockerfile"
+  },
  "features": {
    "ghcr.io/devcontainers/features/rust:1": {}
  },
@@ -1,11 +1,5 @@
 #!/bin/sh

-# Update the underlying (Debian) OS, to make sure we have the latest security patches and libraries like 'GLIBC' 
-sudo apt-get update  && sudo apt-get -y upgrade
-
-# Update pnpm
-#npm install -g pnpm
-
 # Install dependencies
 pnpm install --frozen-lockfile

@@ -4,6 +4,8 @@
 <!-- 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 -->

@@ -39,7 +39,7 @@ jobs:

      - name: Install PNPM
        run: |
-          npm install -g @pnpm/exe@8.14
+          npm install -g @pnpm/exe@8

      - name: Set node
        uses: actions/setup-node@v3
@@ -285,7 +285,7 @@ jobs:

      - name: Install PNPM
        run: |
-          npm install -g @pnpm/exe@8.7.4
+          npm install -g @pnpm/exe@8

      - name: Use Node.js ${{ matrix.node_version }}
        uses: actions/setup-node@v3
@@ -11,7 +11,7 @@ jobs:
    strategy:
      matrix:
        node-version: [18]
-        
+
    steps:
      - name: Checkout
        uses: actions/checkout@v3
@@ -25,7 +25,7 @@ jobs:
        uses: pnpm/action-setup@v2
        id: pnpm-install
        with:
-          version: 7
+          version: 8
          run_install: false

      - name: Get pnpm store directory
@@ -46,8 +46,8 @@ jobs:
        run: pnpm install --no-frozen-lockfile

      - name: Run embeddings script
-        run: pnpm exec nx run tools-documentation-create-embeddings:run-node 
+        run: pnpm exec nx run tools-documentation-create-embeddings:run-node
        env:
            NX_NEXT_PUBLIC_SUPABASE_URL: ${{ secrets.NX_NEXT_PUBLIC_SUPABASE_URL }}
            NX_SUPABASE_SERVICE_ROLE_KEY: ${{ secrets.NX_SUPABASE_SERVICE_ROLE_KEY }}
-            NX_OPENAI_KEY: ${{ secrets.NX_OPENAI_KEY }}
+            NX_OPENAI_KEY: ${{ secrets.NX_OPENAI_KEY }}
@@ -20,7 +20,7 @@ jobs:

      - uses: pnpm/action-setup@v2
        with:
-          version: 8.2
+          version: 8

      - name: Use Node.js ${{ matrix.node_version }}
        uses: actions/setup-node@v3
@@ -19,7 +19,7 @@ jobs:

      - name: Install PNPM
        run: |
-          npm install -g @pnpm/exe@8.3.1
+          npm install -g @pnpm/exe@8

      - name: Run a security audit
        run: pnpm dlx audit-ci --critical --report-type summary
@@ -1,19 +1,121 @@
 name: publish

 on:
+  # Automated schedule - canary releases from master
  schedule:
    - cron: "0 3 * * 2-6" # Tuesdays - Saturdays, at 3am UTC
+  # Manual trigger - PR releases or dry-runs (based on workflow inputs)
  workflow_dispatch:
+    inputs:
+      pr:
+        description: "PR Number - If set, a real release will be created for the branch associated with the given PR number. If blank, a dry-run of the currently selected branch will be performed."
+        required: false
+        type: number
  release:
    types: [ published ]

+# Dynamically generate the display name for the GitHub UI based on the event type and inputs
+run-name: ${{ github.event.inputs.pr && format('PR Release for {0}', github.event.inputs.pr) || github.event_name == 'schedule' && 'Canary Release' || github.event_name == 'workflow_dispatch' && !github.event.inputs.pr && 'Release Dry-Run' || github.ref_name }}
+
 env:
  DEBUG: napi:*
  NX_RUN_GROUP: ${{ github.run_id }}-${{ github.run_attempt }}
  CYPRESS_INSTALL_BINARY: 0
+  NODE_VERSION: 18
+  PNPM_VERSION: 8.15.7 # Aligned with root package.json (pnpm/action-setup will helpfully error if out of sync)

 jobs:
+  # We first need to determine the version we are releasing, and if we need a custom repo or ref to use for the git checkout in subsequent steps.
+  # These values depend upon the event type that triggered the workflow:
+  #
+  # - schedule:
+  #   - We are running a canary release which always comes from the master branch, we can use default ref resolution
+  #     in actions/checkout. The exact version will be generated within scripts/nx-release.ts.
+  #
+  # - release:
+  #   - We are running a full release which is based on the tag that triggered the release event, we can use default
+  #     ref resolution in actions/checkout. The exact version will be generated within scripts/nx-release.ts.
+  #
+  # - workflow_dispatch:
+  #   - We are either running a dry-run on the current branch, in which case the version will be statica and we can use
+  #     default ref resolution in actions/checkout, or we are creating a PR release for the given PR number, in which case
+  #     we should generate an applicable version number within publish-resolve-data.js and use a custom ref of the PR branch name.
+  resolve-required-data:
+    name: Resolve Required Data
+    if: ${{ github.repository_owner == 'nrwl' }}
+    runs-on: ubuntu-latest
+    outputs:
+      version: ${{ steps.script.outputs.version }}
+      dry_run_flag: ${{ steps.script.outputs.dry_run_flag }}
+      success_comment: ${{ steps.script.outputs.success_comment }}
+      publish_branch: ${{ steps.script.outputs.publish_branch }}
+      ref: ${{ steps.script.outputs.ref }}
+      repo: ${{ steps.script.outputs.repo }}
+    env:
+      NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+    steps:
+      # Default checkout on the triggering branch so that the latest publish-resolve-data.js script is available
+      - uses: actions/checkout@v4
+
+      # Set up pnpm and node so that we can verify our setup and that the NPM_TOKEN secret will work later
+      - uses: pnpm/action-setup@v4
+        with:
+          version: ${{ env.PNPM_VERSION }}
+
+      - name: Setup node
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+          registry-url: 'https://registry.npmjs.org'
+          check-latest: true
+
+      # Ensure that the NPM_TOKEN secret is still valid before wasting any time deriving data or building projects
+      - name: Check NPM Credentials
+        run: npm whoami && echo "NPM credentials are valid" || (echo "NPM credentials are invalid or have expired." && exit 1)
+
+      - name: Resolve and set checkout and version data to use for release
+        id: script
+        uses: actions/github-script@v7
+        env:
+          PR_NUMBER: ${{ github.event.inputs.pr }}
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const script = require('${{ github.workspace }}/scripts/publish-resolve-data.js');
+            await script({ github, context, core });
+
+      - name: (PR Release Only) Check out latest master
+        if: ${{ steps.script.outputs.ref != '' }}
+        uses: actions/checkout@v4
+        with:
+          # Check out the latest master branch to get its copy of nx-release.ts
+          repository: nrwl/nx
+          ref: master
+          path: latest-master-checkout
+
+      - name: (PR Release Only) Check out PR branch
+        if: ${{ steps.script.outputs.ref != '' }}
+        uses: actions/checkout@v4
+        with:
+          # Check out the PR branch to get its copy of nx-release.ts
+          repository: ${{ steps.script.outputs.repo }}
+          ref: ${{ steps.script.outputs.ref }}
+          path: pr-branch-checkout
+
+      - name: (PR Release Only) Ensure that nx-release.ts has not changed in the PR being released
+        if: ${{ steps.script.outputs.ref != '' }}
+        env:
+          FILE_TO_COMPARE: "scripts/nx-release.ts"
+        run: |
+          if ! cmp -s "latest-master-checkout/${{ env.FILE_TO_COMPARE }}" "pr-branch-checkout/${{ env.FILE_TO_COMPARE }}"; then
+            echo "🛑 Error: The file ${{ env.FILE_TO_COMPARE }} is different on the ${{ steps.script.outputs.ref }} branch on ${{ steps.script.outputs.repo }} vs latest master on nrwl/nx, cancelling workflow. If you did not modify the file, then you likely just need to rebase/merge latest master."
+            exit 1
+          else
+            echo "✅ The file ${{ env.FILE_TO_COMPARE }} is identical between the ${{ steps.script.outputs.ref }} branch on ${{ steps.script.outputs.repo }} and latest master on nrwl/nx."
+          fi
+
  build:
+    needs: [resolve-required-data]
    if: ${{ github.repository_owner == 'nrwl' }}
    strategy:
      fail-fast: false
@@ -73,7 +175,7 @@ jobs:
              sudo apt-get update
              sudo apt-get install gcc-arm-linux-gnueabihf -y
            build: |
-              pnpm nx run-many --target=build-native -- --target=armv7-unknown-linux-gnueabihf
+              CARGO_TARGET_ARMV7_UNKNOWN_LINUX_GNUEABIHF_LINKER=/usr/bin/arm-linux-gnueabihf-gcc pnpm nx run-many --target=build-native -- --target=armv7-unknown-linux-gnueabihf
          # Android (not needed)
          # - host: ubuntu-latest
          #   target: aarch64-linux-android
@@ -100,16 +202,19 @@ jobs:
    runs-on: ${{ matrix.settings.host }}
    steps:
      - uses: actions/checkout@v4
-
-      - uses: pnpm/action-setup@v2
        with:
-          version: 8
+          repository: ${{ needs.resolve-required-data.outputs.repo }}
+          ref: ${{ needs.resolve-required-data.outputs.ref }}
+
+      - uses: pnpm/action-setup@v4
+        with:
+          version: ${{ env.PNPM_VERSION }}

      - name: Setup node
        uses: actions/setup-node@v4
        if: ${{ !matrix.settings.docker }}
        with:
-          node-version: 18
+          node-version: ${{ env.NODE_VERSION }}
          check-latest: true
          cache: 'pnpm'

@@ -120,7 +225,7 @@ jobs:
          targets: ${{ matrix.settings.target }}

      - name: Cache cargo
-        uses: actions/cache@v3
+        uses: actions/cache@v4
        with:
          path: |
            ~/.cargo/registry/index/
@@ -129,30 +234,36 @@ jobs:
            .cargo-cache
            target/
          key: ${{ matrix.settings.target }}-cargo-registry
+
      - uses: goto-bus-stop/setup-zig@v2
        if: ${{ matrix.settings.target == 'armv7-unknown-linux-gnueabihf' }}
        with:
          version: 0.10.0
+
      - name: Setup toolchain
        run: ${{ matrix.settings.setup }}
        if: ${{ matrix.settings.setup }}
        shell: bash
+
      - name: Setup node x86
        if: matrix.settings.target == 'i686-pc-windows-msvc'
        run: yarn config set supportedArchitectures.cpu "ia32"
        shell: bash
+
      - name: Install dependencies
        if: ${{ !matrix.settings.docker }}
        run: pnpm install --frozen-lockfile
        timeout-minutes: 30
+
      - name: Setup node x86
        uses: actions/setup-node@v4
        if: matrix.settings.target == 'i686-pc-windows-msvc'
        with:
-          node-version: 18
+          node-version: ${{ env.NODE_VERSION }}
          check-latest: true
          cache: pnpm
          architecture: x86
+
      - name: Build in docker
        uses: addnab/docker-run-action@v3
        if: ${{ matrix.settings.docker }}
@@ -160,29 +271,38 @@ jobs:
          image: ${{ matrix.settings.docker }}
          options: --user 0:0 -v ${{ github.workspace }}/.cargo-cache/git/db:/usr/local/cargo/git/db -v ${{ github.workspace }}/.cargo/registry/cache:/usr/local/cargo/registry/cache -v ${{ github.workspace }}/.cargo/registry/index:/usr/local/cargo/registry/index -v ${{ github.workspace }}:/build -w /build
          run: ${{ matrix.settings.build }}
+
      - name: Build
        run: ${{ matrix.settings.build }}
        if: ${{ !matrix.settings.docker }}
        shell: bash
+
      - name: Upload artifact
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
        with:
          name: bindings-${{ matrix.settings.target }}
-          path: packages/**/*.node
+          path: |
+            packages/**/*.node
+            packages/**/*.wasm
          if-no-files-found: error

  build-freebsd:
+    needs: [resolve-required-data]
    if: ${{ github.repository_owner == 'nrwl' }}
-    runs-on: macos-13-large
+    runs-on: ubuntu-latest
    name: Build FreeBSD
    timeout-minutes: 45
    steps:
      - uses: actions/checkout@v4
-        if: ${{ github.event_name != 'schedule' }}
+        if: ${{ github.event_name != 'schedule' && !github.event.inputs.pr }}
+        with:
+          repository: ${{ needs.resolve-required-data.outputs.repo }}
+          ref: ${{ needs.resolve-required-data.outputs.ref }}
+
      - name: Build
        id: build
-        if: ${{ github.event_name != 'schedule' }}
-        uses: cross-platform-actions/action@v0.22.0
+        if: ${{ github.event_name != 'schedule' && !github.event.inputs.pr }}
+        uses: cross-platform-actions/action@v0.25.0
        env:
          DEBUG: napi:*
          RUSTUP_IO_THREADS: 1
@@ -190,14 +310,14 @@ jobs:
          PLAYWRIGHT_BROWSERS_PATH: 0
        with:
          operating_system: freebsd
-          version: '13.2'
+          version: '14.0'
          architecture: x86-64
          environment_variables: DEBUG RUSTUP_IO_THREADS CI NX_PREFER_TS_NODE PLAYWRIGHT_BROWSERS_PATH
          shell: bash
          run: |
            env
            whoami
-            sudo pkg install -y -f node libnghttp2 npm git
+            sudo pkg install -y -f node libnghttp2 www/npm git
            sudo npm install --location=global --ignore-scripts pnpm@8.15.7
            curl https://sh.rustup.rs -sSf --output rustup.sh
            sh rustup.sh -y --profile minimal --default-toolchain stable
@@ -213,8 +333,6 @@ jobs:
            whoami
            env
            freebsd-version
-            mkdir -p /Users/runner/work/_temp/_github_workflow
-            echo "{}" > /Users/runner/work/_temp/_github_workflow/event.json
            pnpm install --frozen-lockfile --ignore-scripts
            pnpm nx run-many --verbose --outputStyle stream --target=build-native -- --target=x86_64-unknown-freebsd
            pnpm nx reset
@@ -223,9 +341,10 @@ jobs:
            echo "KILL ALL NODE PROCESSES"
            killall node || true
            echo "COMPLETE"
+
      - name: Upload artifact
-        if: ${{ github.event_name != 'schedule' }}
-        uses: actions/upload-artifact@v3
+        if: ${{ github.event_name != 'schedule' && !github.event.inputs.pr }}
+        uses: actions/upload-artifact@v4
        with:
          name: bindings-freebsd
          path: packages/**/*.node
@@ -238,7 +357,9 @@ jobs:
    permissions:
      id-token: write
      contents: write
+      pull-requests: write
    needs:
+      - resolve-required-data
      - build-freebsd
      - build
    env:
@@ -247,51 +368,93 @@ jobs:
      NPM_CONFIG_PROVENANCE: true
    steps:
      - uses: actions/checkout@v4
-      - uses: pnpm/action-setup@v2
        with:
-          version: 8
+          repository: ${{ needs.resolve-required-data.outputs.repo }}
+          ref: ${{ needs.resolve-required-data.outputs.ref }}
+
+      - uses: pnpm/action-setup@v4
+        with:
+          version: ${{ env.PNPM_VERSION }}
+
      - name: Setup node
        uses: actions/setup-node@v4
        with:
-          node-version: 18
+          node-version: ${{ env.NODE_VERSION }}
          registry-url: 'https://registry.npmjs.org'
          check-latest: true
          cache: 'pnpm'
-      - name: Check NPM Credentials
-        run: npm whoami && echo "NPM credentials are valid" || (echo "NPM credentials are invalid or have expired." && exit 1)
+
      - name: Install dependencies
        run: pnpm install --frozen-lockfile
+
      - name: Download all artifacts
-        uses: actions/download-artifact@v3
+        uses: actions/download-artifact@v4
        with:
          path: artifacts
+
+      # This command will appropriately fail if no artifacts are available
      - name: List artifacts
        run: ls -R artifacts
        shell: bash
+      - name: Build Wasm
+        run: pnpm build:wasm
      - name: Publish
+        env:
+          VERSION: ${{ needs.resolve-required-data.outputs.version }}
+          DRY_RUN: ${{ needs.resolve-required-data.outputs.dry_run_flag }}
+          PUBLISH_BRANCH: ${{ needs.resolve-required-data.outputs.publish_branch }}
        run: |
-          git checkout -b publish/$GITHUB_REF_NAME
-          # If triggered by the cron, create a canary release
-          if [ "${{ github.event_name }}" = "schedule" ]; then
-            VERSION="canary"
-          else
-            # Otherwise, use the tag name (if triggered via release), or explicit version (if triggered via workflow_dispatch)
-            VERSION="${GITHUB_REF_NAME}"
-          fi
-          # If triggered via workflow_dispatch, perform a dry-run
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            DRY_RUN="--dry-run"
-          else
-            DRY_RUN=""
-          fi
+          echo ""
+          # Create and check out the publish branch
+          git checkout -b $PUBLISH_BRANCH
+          echo ""
+          echo "Version set to: $VERSION"
+          echo "DRY_RUN set to: $DRY_RUN"
+          echo ""
          pnpm nx-release --local=false $VERSION $DRY_RUN
-      - name: Trigger Docs Release
+
+      - name: (Stable Release Only) Trigger Docs Release
        # Publish docs only on a full release
-        if: ${{ !github.event.release.prerelease }}
-        run: |
-          # The GITHUB_REF_NAME is a full version (i.e. 17.3.2). The branchName will only use the major version number.
-          # We will publish docs to the website branch based on the current tag (i.e. website-17)
-          branchName=website-${GITHUB_REF_NAME%.*.*}
-          # We force recreate the branch in order to always be up to date and avoid merge conflicts within the automated workflow
-          git branch -f $branchName
-          git push -f origin $branchName
+        if: ${{ !github.event.release.prerelease && github.event_name == 'release' }}
+        run: npx ts-node ./scripts/release-docs.ts
+
+      - name: (PR Release Only) Create comment for successful PR release
+        if: success() && github.event.inputs.pr
+        uses: actions/github-script@v7
+        env:
+          SUCCESS_COMMENT: ${{ needs.resolve-required-data.outputs.success_comment }}
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const successComment = JSON.parse(process.env.SUCCESS_COMMENT);
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: ${{ github.event.inputs.pr }},
+              body: successComment
+            });
+
+  pr_failure_comment:
+    # Run this job if it is a PR release, running on the nrwl origin, and any of the required jobs failed
+    if: ${{ github.repository_owner == 'nrwl' && github.event.inputs.pr && always() && contains(needs.*.result, 'failure') }}
+    needs: [resolve-required-data, build, build-freebsd, publish]
+    name: (PR Release Failure Only) Create comment for failed PR release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create comment for failed PR release
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          # This script is intentionally kept inline (and e.g. not generated in publish-resolve-data.js)
+          # to ensure that an error within the data generation itself is not missed.
+          script: |
+            const message = `
+              Failed to publish a PR release of this pull request, triggered by @${{ github.triggering_actor }}. 
+              See the failed workflow run at: https://github.com/nrwl/nx/actions/runs/${{ github.run_id }}
+            `;
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: ${{ github.event.inputs.pr }},
+              body: message
+            });
@@ -37,7 +37,7 @@ out
 .angular

 # Local dev files
-.env
+.env.local
 .bashrc
 .nx

@@ -46,6 +46,7 @@ out
 # Fix for issue when working on the repo in a dev container
 .pnpm-store
 .nx/cache
+.nx/workspace-data

 .cargo/.package-cache
 .cargo/bin/
@@ -55,3 +56,5 @@ out
 .npm/
 .profile
 .rustup/
+target
+*.wasm
@@ -11,24 +11,24 @@ launch-templates:
      NPM_CONFIG_PREFIX: '/home/workflows/.npm-global'
    init-steps:
      - name: Checkout
-        uses: 'nrwl/nx-cloud-workflows/v3.6/workflow-steps/checkout/main.yaml'
+        uses: 'nrwl/nx-cloud-workflows/v4/workflow-steps/checkout/main.yaml'
      - name: Cache restore
-        uses: 'nrwl/nx-cloud-workflows/v3.6/workflow-steps/cache/main.yaml'
-        env:
-          KEY: 'pnpm-lock.yaml'
-          PATHS: |
+        uses: 'nrwl/nx-cloud-workflows/v4/workflow-steps/cache/main.yaml'
+        inputs:
+          key: 'pnpm-lock.yaml'
+          paths: |
            node_modules
            ~/.cache/Cypress
            ~/.cache/ms-playwright
            ~/.pnpm-store
-          BASE_BRANCH: 'master'
+          base-branch: 'master'
      - name: Install e2e deps
        script: |
          sudo apt-get update
-          sudo apt-get install -y ca-certificates lsof
+          sudo apt-get install -y ca-certificates lsof libvips-dev libglib2.0-dev libgirepository1.0-dev
      - name: Install Pnpm
        script: |
-          npm install -g pnpm@8.15.5
+          npm install -g pnpm@8

      - name: Pnpm Install
        script: |
@@ -17,6 +17,11 @@ packages/nx/src/plugins/js/lock-file/__fixtures__/**/*.*
 packages/**/schematics/**/files/**/*.html
 packages/**/generators/**/files/**/*.html
 packages/nx/src/native/**/*.rs
+packages/nx/src/native/browser.js
+packages/nx/src/native/nx.wasi-browser.js
+packages/nx/src/native/nx.wasi.cjs
+packages/nx/src/native/wasi-worker-browser.mjs
+packages/nx/src/native/wasi-worker.mjs
 packages/nx/src/native/native-bindings.js
 packages/nx/src/native/index.d.ts
 nx-dev/nx-dev/.next/
@@ -40,3 +45,5 @@ CODEOWNERS
 /.nx/cache

 .pnpm-store
+
+/.nx/workspace-data
@@ -76,13 +76,13 @@ Check out [this video for a live walkthrough](https://youtu.be/Tx257WpNsxc) or f
 - Run `pnpm local-registry` in Terminal 1 (keep it running)
 - Run `npm adduser --registry http://localhost:4873` in Terminal 2 (real credentials are not required, you just need to
  be logged in. You can use test/test/test@test.io.)
- Run `pnpm nx-release 18.0.0 --local` in Terminal 2 - you can choose any nonexistent version number here, but it's recommended to use the next major
+- Run `pnpm nx-release 20.0.0 --local` in Terminal 2 - you can choose any nonexistent version number here, but it's recommended to use the next major
 - Run `cd ./tmp` in Terminal 2
- Run `npx create-nx-workspace@18.0.0` in Terminal 2
+- Run `npx create-nx-workspace@20.0.0` in Terminal 2

 If you have problems publishing, make sure you use Node 18 and NPM 8.

-**NOTE:** To use this newly published local version, you need to make a new workspace, run `nx migrate` or change all of your target packages to this new version, eg: `"nx": "^18.0.0",` and re-run `pnpm i` in your testing project.
+**NOTE:** To use this newly published local version, you need to make a new workspace, run `nx migrate` or change all of your target packages to this new version, eg: `"nx": "^20.0.0",` and re-run `pnpm i` in your testing project.

 ### Publishing for Yarn 2+ (Berry)

@@ -355,3 +355,7 @@ Closes #157
 To simplify and automate the process of committing with this format,
 **Nx is a [Commitizen](https://github.com/commitizen/cz-cli) friendly repository**, just do `git add` and
 execute `pnpm commit`.
+
+#### PR releases
+
+If you are working on a particularly complex change or feature addition, you can request a dedicated Nx release for the associated 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.
@@ -29,7 +29,7 @@ A few links to help you get started:
 - [Nx.Dev: Core Tutorials](https://nx.dev/getting-started/intro)
 - [Recipe: Adding Nx to an Existing Monorepo](https://nx.dev/recipes/adopting-nx/adding-to-monorepo)
 - [Official Nx YouTube Channel](https://www.youtube.com/@NxDevtools)
- [Blog Posts About Nx](https://blog.nrwl.io/nx/home)
+- [Blog Posts About Nx](https://nx.dev/blog)

 <p style="text-align: center;"><a href="https://nx.dev/#learning-materials" target="_blank" rel="noreferrer"><img src="./images/nx-courses-and-videos.svg" 
 width="100%" alt="Nx - Smart Monorepos · Fast CI"></a></p>
@@ -77,12 +77,12 @@
  {
    "name": "@nxext/ionic-react",
    "description": "An Nx plugin for developing Ionic React applications and libraries",
-    "url": "https://github.com/nxext/nx-extensions/tree/main/packages/ionic-react"
+    "url": "https://github.com/nxext/nx-extensions-ionic/tree/main/packages/ionic-react"
  },
  {
    "name": "@nxext/ionic-angular",
    "description": "An Nx plugin for developing Ionic Angular applications and libraries",
-    "url": "https://github.com/nxext/nx-extensions/tree/main/packages/ionic-angular"
+    "url": "https://github.com/nxext/nx-extensions-ionic/tree/main/packages/ionic-angular"
  },
  {
    "name": "@nxext/capacitor",
@@ -299,6 +299,11 @@
    "description": "Nx plugin for working with shadcn/ui",
    "url": "https://github.com/tripss/nx-extend/tree/master/packages/shadcn-ui"
  },
+  {
+    "name": "@nx-extend/docusaurus",
+    "description": "Nx plugin adding first class support for Docusaurus in your Nx workspace.",
+    "url": "https://github.com/tripss/nx-extend/tree/master/packages/docusaurus"
+  },
  {
    "name": "@nativescript/nx",
    "description": "Nx Plugin adding first class support for NativeScript in your Nx workspace",
@@ -183,6 +183,14 @@ To display a terminal command, use:
 ‎```
 ````

+You can also add a title to the shell as follows:
+
+````
+‎```shell {% title="Build the app" %}
+‎ npx nx build
+‎```
+````
+
 #### Terminal Output

 You can display your terminal output with a dedicated component the same way you would show code.
@@ -408,3 +416,22 @@ Embed an Nx Graph visualization that can be panned by the user.

 {% /graph %}
 ````
+
+## Publishing Process
+
+There are multiple versions of the `nx.dev` site.
+
+- [canary.nx.dev](https://canary.nx.dev) contains the documentation on the `master` branch
+- [nx.dev](https://nx.dev) contains the documentation as of the latest release of Nx to npm. The main site will not include reference documentation for APIs that have been merged to the codebase, but not yet released to the public.
+- `[version].nx.dev` contains the documentation for that version of Nx. `[version]` in this case is the major version up to the current LTS version of Nx. So [18.nx.dev](https://18.nx.dev) will show the Nx documentation as of the last released version of Nx 18.
+
+When a commit that contains documentation is merged into `master`, it will be immediately published to `canary.nx.dev`. Whenever a new release of Nx is published to npm, that documentation will then be available on the main site.
+
+### Immediately Publishing Time-Sensitive Documentation
+
+If you have a documentation change that should be published immediately, you'll need to create 2 PRs.
+
+1. First, create a PR against `master` in the normal manner.
+2. Your second PR needs to be made against the website branch with the latest major version of Nx. So your second PR can be created against `website-19` if the latest version of Nx is `19.1.0`. Once `website-19` is updated with your changes, the main `nx.dev` site will be updated.
+
+Later, when Nx `19.1.1` is released, `website-19` will be overwritten with whatever is on `master` and the first PR you created will take effect.
@@ -1,5 +1,6 @@
 ---
 title: Nx Cloud 3.0 — Faster Cache, More Powerful DTE, Better Ergonomics
+slug: 'nx-cloud-3-0-faster-more-efficient-modernized'
 authors: [Juri Strumpflohner]
 cover_image: '/blog/images/2023-04-19/featured_img.webp'
 tags: [nx, nx-cloud]
@@ -116,6 +117,6 @@ In addition, we are actively exploring ways to provide advanced analytics for yo
 - [Nx Docs](/getting-started/intro)
 - [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,5 +1,6 @@
 ---
 title: Nx Console gets Lit
+slug: 'nx-console-gets-lit'
 authors: [Max Kless]
 cover_image: '/blog/images/2023-06-29/featured_img.webp'
 tags: [nx, nx-console]
@@ -332,6 +333,6 @@ If the prettier UI and better performance haven’t convinced you, this surely w
 - [Nx Docs](/getting-started/intro)
 - [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,5 +1,6 @@
 ---
 title: Qwikify your Development with Nx
+slug: 'qwikify-your-development-with-nx'
 authors: ['Colum Ferry']
 cover_image: '/blog/images/2023-08-15/featured_img.png'
 tags: [nx, changelog, release]
@@ -0,0 +1,21 @@
+---
+title: Nx Raises $16M Series A
+slug: 'nx-raises-16m-series-a'
+authors: [Jeff Cross]
+tags: [nx]
+---
+
+Victor and I are excited to announce that Nx has raised another $16M in a Series A funding round with Nexus Venture Partners and a16z! See our announcement video for more, and be sure to check out the [live stream of Nx Conf 2023](https://youtube.com/live/IQ5YyEYZw68?feature=share) tomorrow to see what we’re up to!
+
+{% youtube src="https://www.youtube.com/embed/KuyYhC4ClW8?si=qoZL6i6X1E7wjChD" %}
+
+---
+
+## Learn more
+
+- [Nx Docs](/getting-started/intro)
+- [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
+- [Nx GitHub](https://github.com/nrwl/nx)
+- [Nx Official Discord Server](https://go.nx.dev/community)
+- [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
+- [Speed up your CI](https://nx.app/)
@@ -1,5 +1,6 @@
 ---
 title: Nx Conf 2023 — Recap
+slug: 'nx-conf-2023-recap'
 authors: [Juri Strumpflohner]
 cover_image: '/blog/images/2023-10-13/featured_img.webp'
 tags: [nx, nx-conf]
@@ -475,7 +476,7 @@ Jon and Max are the masterminds behind [Nx Console](/getting-started/editor-setu

 They mention the release of the JetBrains IDE support earlier this year and give a big shoutout to [Issam](https://github.com/iguissouma) who was the original author of the Nx Console Webstorm community plugin and who helped a lot with the official Nx Console version for JetBrains IDE.

-Jon and Max demo the new IntelliJ version of Nx console and how it properly integrates as well as how they wrote the new UI completely from the ground up [using Lit](/blog/2023-06-29-nx-console-gets-lit).
+Jon and Max demo the new IntelliJ version of Nx console and how it properly integrates as well as how they wrote the new UI completely from the ground up [using Lit](/blog/nx-console-gets-lit).

 Clearly they did not spare showing off the awesome new graph capabilities built into Nx Console that allow you to directly navigate to files.

@@ -492,6 +493,6 @@ If you enjoyed these, [subscribe to our YouTube channel](https://www.youtube.com
 - [Nx Docs](/getting-started/intro)
 - [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,12 +1,11 @@
 ---
 title: 'Nx 17 has Landed'
+slug: 'nx-17-release'
 authors: ['Juri Strumpflohner', 'Zack DeRose']
 cover_image: '/blog/images/2023-10-20/featured_img.png'
 tags: [nx, design]
 ---

-{% youtube src="https://www.youtube.com/embed/1Z0iA9K1o8M?si=9XxIboXSZ5yxFpIt" /%}
-
 We’re excited to announce the release of Nx version 17!

 This article will cover the main things you need to know to get the most out of Nx 17!
@@ -26,6 +25,12 @@ Here’s a Table of Contents so you can skip straight to the updates you care ab
 - [Experimental: Nx Project Inference API v2](#experimental-nx-project-inference-api-v2)
 - [20k Github Stars!!](#20k-github-stars)

+**Prefer a video?**
+
+{% youtube src="https://www.youtube.com/embed/1Z0iA9K1o8M?si=9XxIboXSZ5yxFpIt" /%}
+
+---
+
 ## It’s a Vue-tiful Day for Nx!

 Ever since we added Vite as a first-class citizen to Nx workspaces (see `@nx/vite`), we started falling in love with the Vue community. The only logical next step: Nx now provides a brand new Vue plugin that is being maintained by the Nx team! (And we're already working on a [Nuxt](https://nuxt.com/) plugin 🤫)
@@ -178,7 +183,7 @@ We’ve been working hard at reducing and simplifying all the configuration requ

 At Nx Conf in New York City, we unveiled the next big step for Nx: **Nx Workflows**.

-If you missed it, Simon Critchley walks you through in his [Nx Conf](https://dev.to/nx/nx-conf-2023-recap-53ep) talk:
+If you missed it, Simon Critchley walks you through in his [Nx Conf](/blog/nx-conf-2023-recap) talk:

 {% youtube src="https://www.youtube.com/embed/JG1FWfZFByM?si=7_NzxJP8nA7RbFhl" /%}

@@ -226,7 +231,7 @@ In Nx 17, we removed any remaining traces of `tslint` from our linter package, s

 As we solidify this command, we intend to bring robust support for various versioning and publishing strategies, as well as built-in support for publishing packages or modules to a variety of languages, registries, and platforms.

-For more [checkout our API docs](/nx-api/nx/documents/release), and be sure to catch James Henry’s announcement of this new command at [Nx Conf](https://dev.to/nx/nx-conf-2023-recap-53ep):
+For more [checkout our API docs](/nx-api/nx/documents/release), and be sure to catch James Henry’s announcement of this new command at [Nx Conf](/blog/nx-conf-2023-recap):

 {% youtube src="https://www.youtube.com/embed/p5qW5-2nKqI?si=FzpGMJwPVINc1hgL" /%}

@@ -0,0 +1,624 @@
+---
+title: State Management Nx React Native/Expo Apps with TanStack Query and Redux
+slug: 'state-management-nx-react-native-expo-apps-with-tanstack-query-and-redux'
+authors: [Emily Xiong]
+image: '/blog/images/2023-11-08/featured_img.webp'
+tags: [nx, React Native]
+---
+
+There are currently countless numbers of state management libraries out there. This blog will show you how to use state management for React Native in Nx monorepo with [TanStack Query](https://tanstack.com/query/latest) (which happens to use [Nx on their repo](https://cloud.nx.app/orgs/6412ca9d1c251d000efa21ba/workspaces/6412c827e6da5d7b4a0b1fe3/overview)) and Redux.
+
+This blog will show:
+
+- How to set up these libraries and their dev tools
+- How to build the sample page below in React Native / Expo with state management
+- How to do unit testing
+
+It will call an API and show a cat fact on the page, allowing users to like or dislike the data.
+
+![](/blog/images/2023-11-08/bodyimg1.webp)
+
+Github repo: [https://github.com/xiongemi/nx-expo-monorepo](https://github.com/xiongemi/nx-expo-monorepo)
+
+---
+
+## Before We Start
+
+From [TanStack Query documentation](https://tanstack.com/query/latest/docs/framework/react/guides/does-this-replace-client-state), it says:
+
+- [TanStack Query](https://tanstack.com/query/latest/docs/framework/react/overview) is a **server-state** library.
+- [Redux](https://redux.js.org/) is a client-state library.
+
+What is the difference between the server state and the client state?
+
+In short:
+
+- Calling an API, dealing with asynchronous data-> server state
+- Everything else about UI, dealing with synchronous data -> client state
+
+## Installation
+
+To use **[TanStack Query / React Query](https://tanstack.com/query/latest)** for the server state, I need to install:
+
+- Library: [@tanstack/react-query](https://tanstack.com/query/latest)
+- Dev tools: [@tanstack/react-query-devtools](https://tanstack.com/query/latest/docs/framework/react/devtools)
+
+I will use **Redux** for everything else.
+
+- Library: [redux](https://github.com/reduxjs/redux), react-redux, @reduxjs/toolkit
+- Dev tools: [@redux-devtools/extension](https://github.com/zalmoxisus/redux-devtools-extension)
+- Logger: [redux-logger](https://github.com/LogRocket/redux-logger), [@types/redux-logger](https://www.npmjs.com/package/@types/redux-logger)
+- Storage: [redux-persist](https://github.com/rt2zz/redux-persist), [@react-native-async-storage/async-storage](https://github.com/react-native-async-storage/async-storage)
+
+To install all the above packages:
+
+```shell
+#npm
+npm install @tanstack/react-query @tanstack/react-query-devtools redux react-redux @reduxjs/toolkit @redux-devtools/extension redux-logger @types/redux-logger redux-persist @react-native-async-storage/async-storage --save-dev
+
+#yarn
+yarn add @tanstack/react-query @tanstack/react-query-devtools redux react-redux @reduxjs/toolkit @redux-devtools/extension redux-logger @types/redux-logger redux-persist @react-native-async-storage/async-storage --dev
+
+#pnpm
+pnpm add @tanstack/react-query @tanstack/react-query-devtools redux react-redux @reduxjs/toolkit @redux-devtools/extension redux-logger @types/redux-logger redux-persist @react-native-async-storage/async-storage --save-dev
+```
+
+## Server State with React Query
+
+### Setup Devtools
+
+First, you need to add React Query / TanStack Query in the `App.tsx`:
+
+```tsx
+import React from 'react';
+import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
+import { ReactQueryDevtools } from '@tanstack/react-query-devtools';
+import { Platform } from 'react-native';
+
+const App = () => {
+  const queryClient = new QueryClient();
+  return (
+    <QueryClientProvider client={queryClient}>
+      {Platform.OS === 'web' && <ReactQueryDevtools />}
+      ...
+    </QueryClientProvider>
+  );
+};
+
+export default App;
+```
+
+Note: the [React Query Devtools](https://tanstack.com/query/latest/docs/framework/react/devtools) currently do not support react native, and it only works on the web, so there is a condition: `{ Platform.OS === ‘web’ && <ReactQueryDevtools />}.`
+
+For the react native apps, in order to use this tool, you need to use [react-native-web](https://necolas.github.io/react-native-web/) to interpolate your native app to the web app first.
+
+If you open my Expo app on the web by running `nx start cats` and choose the options `Press w │ open web`, you should be able to use the dev tools and see the state of my react queries:
+
+![](/blog/images/2023-11-08/bodyimg2.webp)
+
+Or you can run npx nx serve cats to launch the app in a web browser and debug from there.
+
+### Create a Query
+
+What is a query?
+
+> “A query is a declarative dependency on an asynchronous source of data that is tied to a unique key. A query can be used with any Promise-based method (including GET and POST methods) to fetch data from a server.” [(https://tanstack.com/query/v4/docs/react/guides/queries)](https://tanstack.com/query/v4/docs/react/guides/queries)
+
+Now let’s add our first query. In this example, it will be added under `lib/queries` folder. To create a query to fetch a new fact about cats, run the command:
+
+```shell
+# expo workspace
+npx nx generate @nx/expo:lib use-cat-fact --directory=queries
+
+# react-native workspace
+npx nx generate @nx/react-native:lib use-cat-fact --directory=queries
+```
+
+Or use [Nx Console](/recipes/nx-console):
+
+![](/blog/images/2023-11-08/bodyimg3.webp)
+
+Now notice under libs folder, `use-cat-fact` folder got created under `libs/queries`:
+
+![](/blog/images/2023-11-08/bodyimg4.webp)
+
+If you use React Native CLI, just add a folder in your workspace root.
+
+For this app, let’s use this API: [https://catfact.ninja/](https://catfact.ninja/). At `libs/queries/use-cat-fact/src/lib/use-cat-fact.ts`, add code to fetch the data from this API:
+
+```ts
+import { useQuery } from '@tanstack/react-query';
+
+export const fetchCatFact = async (): Promise<string> => {
+  const response = await fetch('https://catfact.ninja/fact');
+  const data = await response.json();
+  return data.fact;
+};
+
+export const useCatFact = () => {
+  return useQuery({
+    queryKey: ['cat-fact'],
+    queryFn: fetchCatFact,
+    enabled: false,
+  });
+};
+```
+
+Essentially, you have created a custom hook that calls useQuery function from the TanStack Query library.
+
+### Unit Testing
+
+If you render this hook directly and run the unit test with the command `npx nx test queries-use-cat-fact`, this error will show up in the console:
+
+```shell
+Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
+    1. You might have mismatching versions of React and the renderer (such as React DOM)
+    2. You might be breaking the Rules of Hooks
+    3. You might have more than one copy of React in the same app
+    See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
+```
+
+To solve this, you need to wrap your component inside the renderHook function from `@testing-library/react-native` library:
+
+1. **Install Library to Mock Fetch**
+
+Depending on which library you use to make HTTP requests. (e.g. fetch, axios), you need to install a library to mock the response.
+
+- If you use `fetch` to fetch data, you need to install `jest*fetch-mock`.
+- If you use `axios` to fetch data, you need to install `axio*-mock-adapter`.
+
+For this example, since it uses `fetch`, you need to install `jest-fetch-mock`:
+
+```shell
+#npm
+npm install jest-fetch-mock --save-dev
+
+#yarn
+yard add jest-fetch-mock --dev
+```
+
+You also need to mock `fetch` library in `libs/queries/use-cat-fact/test-setup.ts`:
+
+```ts
+import fetchMock from 'jest-fetch-mock';
+
+fetchMock.enableMocks();
+```
+
+2. **Create Mock Query Provider**
+
+In order to test out `useQuery` hook, you need to wrap it inside a mock `QueryClientProvider`. Since this mock query provider is going to be used more than once, let’s create a library for this wrapper:
+
+```shell
+# expo library
+npx nx generate @nx/expo:library test-wrapper --directory=queries
+
+# react native library
+npx nx generate @nx/react-native:library test-wrapper --directory=queries
+```
+
+Then a component inside this library:
+
+```shell
+# expo library
+npx nx generate @nx/expo:component test-wrapper --project=queries-test-wrapper
+
+# react native library
+npx nx generate @nx/react-native:component test-wrapper --project=queries-test-wrapper
+```
+
+Add the mock `QueryClientProvider` in `libs/queries/test-wrapper/src/lib/test-wrapper/test-wrapper.tsx`:
+
+```tsx
+import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
+import React from 'react';
+
+export interface TestWrapperProps {
+  children: React.ReactNode;
+}
+
+export function TestWrapper({ children }: TestWrapperProps) {
+  const queryClient = new QueryClient();
+  return (
+    <QueryClientProvider client={queryClient}>{children}</QueryClientProvider>
+  );
+}
+
+export default TestWrapper;
+```
+
+3. **Use Mock Responses in Unit Test**
+
+Then this is what the unit test for my query would look like:
+
+```tsx
+import { TestWrapper } from '@nx-expo-monorepo/queries/test-wrapper';
+import { renderHook, waitFor } from '@testing-library/react-native';
+import { useCatFact } from './use-cat-fact';
+import fetchMock from 'jest-fetch-mock';
+
+describe('useCatFact', () => {
+  afterEach(() => {
+    jest.resetAllMocks();
+  });
+
+  it('status should be success', async () => {
+    // simulating a server response
+    fetchMock.mockResponseOnce(
+      JSON.stringify({
+        fact: 'random cat fact',
+      })
+    );
+
+    const { result } = renderHook(() => useCatFact(), {
+      wrapper: TestWrapper,
+    });
+    result.current.refetch(); // refetching the query
+    expect(result.current.isLoading).toBeTruthy();
+
+    await waitFor(() => expect(result.current.isLoading).toBe(false));
+    expect(result.current.isSuccess).toBe(true);
+    expect(result.current.data).toEqual('random cat fact');
+  });
+
+  it('status should be error', async () => {
+    fetchMock.mockRejectOnce();
+
+    const { result } = renderHook(() => useCatFact(), {
+      wrapper: TestWrapper,
+    });
+    result.current.refetch(); // refetching the query
+    expect(result.current.isLoading).toBeTruthy();
+
+    await waitFor(() => expect(result.current.isLoading).toBe(false));
+    expect(result.current.isError).toBe(true);
+  });
+});
+```
+
+If you use `axios`, your unit test would look like this:
+
+```tsx
+// If you use axios, your unit test would look like this:
+import { TestWrapper } from '@nx-expo-monorepo/queries/test-wrapper';
+import { renderHook, waitFor } from '@testing-library/react-native';
+import { useCatFact } from './use-cat-fact';
+import axios from 'axios';
+import MockAdapter from 'axios-mock-adapter';
+
+// This sets the mock adapter on the default instance
+const mockAxios = new MockAdapter(axios);
+
+describe('useCatFact', () => {
+  afterEach(() => {
+    mockAxios.reset();
+  });
+
+  it('status should be success', async () => {
+    // simulating a server response
+    mockAxios.onGet().replyOnce(200, {
+      fact: 'random cat fact',
+    });
+
+    const { result } = renderHook(() => useCatFact(), {
+      wrapper: TestWrapper,
+    });
+    result.current.refetch(); // refetching the query
+    expect(result.current.isLoading).toBeTruthy();
+
+    await waitFor(() => expect(result.current.isLoading).toBe(false));
+    expect(result.current.isSuccess).toBe(true);
+    expect(result.current.data).toEqual('random cat fact');
+  });
+
+  it('status should be error', async () => {
+    mockAxios.onGet().replyOnce(500);
+
+    const { result } = renderHook(() => useCatFact(), {
+      wrapper: TestWrapper,
+    });
+    result.current.refetch(); // refetching the query
+    expect(result.current.isLoading).toBeTruthy();
+
+    await waitFor(() => expect(result.current.isLoading).toBe(false));
+    expect(result.current.isError).toBe(true);
+  });
+});
+```
+
+Notice that this file imports `TestWrapper` from `@nx-expo-monorepo/queries/test-wrapper`, and it is added to `renderHook` function with `{ wrapper: TestWrapper }`.
+
+Now you run the test command `nx test queries-use-cat-fact`, it should pass:
+
+```shell
+ PASS   queries-use-cat-fact  libs/queries/use-cat-fact/src/lib/use-cat-fact.spec.ts (5.158 s)
+  useCatFact
+    ✓ status should be success (44 ms)
+    ✓ status should be error (96 ms)
+```
+
+### Integrate with Component
+
+Currently `userQuery` returns the following properties:
+
+- `isLoading` or `status === 'loading'` - The query has no data yet
+- `isError` or `status === 'error'` - The query encountered an error
+- `isSuccess` or `status === 'success'` - The query was successful and data is available
+
+Now with components controlled by the server state, you can leverage the above properties and change your component to follow the below pattern:
+
+```ts
+export interface CarouselProps {
+  isError: boolean;
+  isLoading: boolean;
+  isSuccess: boolean;
+}
+
+
+export function Carousel({
+  isSuccess,
+  isError,
+  isLoading,
+}: CarouselProps) {
+  return (
+    <>
+      {isSuccess && (
+        ...
+      )}
+      {isLoading && (
+        ...
+      )}
+      {isError && (
+        ...
+      )}
+    </>
+  );
+}
+
+export default Carousel;
+```
+
+Then in the parent component, you can use the query created above:
+
+```tsx
+import { useCatFact } from '@nx-expo-monorepo/queries/use-cat-fact';
+import { Carousel } from '@nx-expo-monorepo/ui';
+import React from 'react';
+
+export function Facts() {
+  const { data, isLoading, isSuccess, isError, refetch, isFetching } =
+    useCatFact();
+
+  return (
+    <Carousel
+      content={data}
+      isLoading={isLoading || isFetching}
+      isSuccess={isSuccess}
+      isError={isError}
+      onReload={refetch}
+    >
+    ...
+   );
+}
+```
+
+If you serve the app on the web and open the [React Query Devtools](https://tanstack.com/query/v4/docs/framework/react/devtools), you should be able to see the query I created `cat-fact` and data in the query.
+
+![](/blog/images/2023-11-08/bodyimg5.webp)
+
+---
+
+## Redux
+
+### Create a Library
+
+First, you need to create a library for redux:
+
+```shell
+# expo library
+npx nx generate @nx/expo:lib cat --directory=states
+
+# react native library
+npx nx generate @nx/react-native:lib cat --directory=states
+```
+
+This should create a folder under libs:
+
+![](/blog/images/2023-11-08/bodyimg6.webp)
+
+### Create a State
+
+For this app, it is going to track when users click the like button, so you need to create a state called `likes`.
+
+![](/blog/images/2023-11-08/bodyimg7.webp)
+
+You can use the [Nx Console](/recipes/nx-console) to create a redux slice:
+
+![](/blog/images/2023-11-08/bodyimg8.webp)
+
+Or run this command:
+
+```shell
+npx nx generate @nx/react:redux likes --project=states-cat --directory=likes
+```
+
+Then update the redux slice at `libs/states/cat/src/lib/likes/likes.slice.ts`:
+
+```ts
+import {
+  createEntityAdapter,
+  createSelector,
+  createSlice,
+  EntityState,
+} from '@reduxjs/toolkit';
+
+export const LIKES_FEATURE_KEY = 'likes';
+
+export interface LikesEntity {
+  id: string;
+  content: string;
+  dateAdded: number;
+}
+
+export type LikesState = EntityState<LikesEntity>;
+
+export const likesAdapter = createEntityAdapter<LikesEntity>();
+
+export const initialLikesState: LikesState = likesAdapter.getInitialState();
+
+export const likesSlice = createSlice({
+  name: LIKES_FEATURE_KEY,
+  initialState: initialLikesState,
+  reducers: {
+    like: likesAdapter.addOne,
+    remove: likesAdapter.removeOne,
+    clear: likesAdapter.removeAll,
+  },
+});
+
+/*
+ * Export reducer for store configuration.
+ */
+export const likesReducer = likesSlice.reducer;
+
+export const likesActions = likesSlice.actions;
+
+const { selectAll } = likesAdapter.getSelectors();
+
+const getlikesState = <ROOT extends { likes: LikesState }>(
+  rootState: ROOT
+): LikesState => rootState[LIKES_FEATURE_KEY];
+
+const selectAllLikes = createSelector(getlikesState, selectAll);
+
+export const likesSelectors = {
+  selectAllLikes,
+};
+```
+
+Every time the “like” button gets clicked, you want to store the content of what users liked. So you need to create an entity to store this information.
+
+```ts
+export interface LikesEntity {
+  id: string;
+  content: string;
+  dateAdded: number;
+}
+```
+
+This state has 3 actions:
+
+- like: when users click like
+- remove: when users cancel the like
+- clear: when users clear all the likes
+
+### Root Store
+
+Then you have to add the root store and create a transform function to stringify the redux state:
+
+```html
+<script src="https://gist.github.com/xiongemi/5f364d84f89b647dcaaf7e5437ea789c.js"></script>
+```
+
+### Connect Redux State with UI
+
+Then in `apps/cats/src/app/App.tsx`, you have to:
+
+- wrap the app inside the `StoreProvider` with the root store to connect with the Redux state.
+- wrap the app inside `PersistGate` to persist the redux state in the storage
+
+```tsx
+import React from 'react';
+import AsyncStorage from '@react-native-async-storage/async-storage';
+import { PersistGate } from 'redux-persist/integration/react';
+import {
+  createRootStore,
+  transformEntityStateToPersist,
+} from '@nx-expo-monorepo/states/cat';
+import { Loading } from '@nx-expo-monorepo/ui';
+import { Provider as StoreProvider } from 'react-redux';
+
+const App = () => {
+  const persistConfig = {
+    key: 'root',
+    storage: AsyncStorage,
+    transforms: [transformEntityStateToPersist],
+  };
+  const { store, persistor } = createRootStore(persistConfig);
+
+  return (
+    <PersistGate loading={<Loading />} persistor={persistor}>
+      <StoreProvider store={store}>...</StoreProvider>
+    </PersistGate>
+  );
+};
+
+export default App;
+```
+
+In your component where the like button is located, you need to dispatch the like action. I created a file at `apps/cats/src/app/facts/facts.props.ts`:
+
+```ts
+import {
+  likesActions,
+  LikesEntity,
+  RootState,
+} from '@nx-expo-monorepo/states/cat';
+import { AnyAction, ThunkDispatch } from '@reduxjs/toolkit';
+
+const mapDispatchToProps = (
+  dispatch: ThunkDispatch<RootState, void, AnyAction>
+) => {
+  return {
+    like(item: LikesEntity) {
+      dispatch(likesActions.like(item));
+    },
+  };
+};
+
+type mapDispatchToPropsType = ReturnType<typeof mapDispatchToProps>;
+
+type FactsProps = mapDispatchToPropsType;
+
+export { mapDispatchToProps };
+export type { FactsProps };
+```
+
+Now you have passed the `like` function to the props of the facts component. Now inside the facts component, you can call the like function from props to dispatch the like action.
+
+### Debugging
+
+To debug redux with Expo, I can simply open the Debugger Menu by entering “d” in the console or in the app, then choose the option “Open JS Debugger”.
+
+![](/blog/images/2023-11-08/bodyimg9.webp)
+
+Then you can view my redux logs in the JS Debugger console:
+
+![](/blog/images/2023-11-08/bodyimg10.webp)
+
+Or you can run `npx nx serve cats` to launch the app in web view. Then you can use Redux Devtools and debug the native app like a web app:
+
+![](/blog/images/2023-11-08/bodyimg11.webp)
+
+---
+
+## Summary
+
+Here is a simple app that uses TanStack Query and Redux for state management. These 2 tools are pretty powerful and they manage both server and client state for you, which is easy to scale, test, and debug.
+
+Nx is a powerful monorepo tool. Together with Nx and these 2 state management tools, it will be very easy to scale up any app.
+
+- TanStack Query site: [https://tanstack.com/query/latest](https://tanstack.com/query/latest)
+- Official @nx/expo plugin: [/nx-api/expo](/nx-api/expo)
+- Official @nx/react-native plugin: [/nx-api/react-native](/nx-api/react-native)
+
+---
+
+## Learn more
+
+- [Nx Docs](/getting-started/intro)
+- [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
+- [Nx GitHub](https://github.com/nrwl/nx)
+- [Nx Official Discord Server](https://go.nx.dev/community)
+- [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
+- [Speed up your CI](https://nx.app/)
@@ -0,0 +1,315 @@
+---
+title: Nx Docs AI Assistant
+slug: 'nx-docs-ai-assistant'
+authors: [Katerina Skroumpelou]
+cover_image: '/blog/images/2023-11-21/featured_img.webp'
+tags: [nx, docs, AI]
+---
+
+## Introduction
+
+The [Nx Docs AI Assistant](/ai-chat) is a tool designed to provide users with answers straight from the Nx documentation. In this article I will explain how it is built, and how we ensure accuracy and relevance.
+
+In the end of this document I have added a [“glossary”](#glossary) of terms that are used throughout this document.
+
+## Why have an AI assistant for documentation?
+
+First of all, let’s answer this simple question: why do you need an AI assistant for a documentation site in the first place? Using an AI assistant for documentation search and retrieval can offer a number of benefits for both users and authors. For users, the challenges of navigating through a large volume and density of documentation are alleviated. Unlike static keyword matching, AI enables more personalized and contextual search, allowing for more complex or sophisticated queries beyond simple keywords. This creates a dynamic feedback loop where users can ask follow-up questions, mix and combine documents, and ultimately enjoy an enhanced user experience that goes beyond basic documentation retrieval.
+
+For authors, a docs AI assistant provides valuable insights into user behavior. It can identify the questions users are frequently asking, pointing to areas where more documentation may be needed. Additionally, if the AI consistently provides unsatisfactory or incorrect responses to certain queries, it could highlight unclear or lacking portions of the documentation. This not only allows for targeted improvements but also makes more parts of the documentation easily accessible to users through intelligent linking. Overall, it can enrich user interaction and help with future content strategy.
+
+## The Nx Docs AI Assistant Workflow
+
+### Overview
+
+In a nutshell, the Nx Docs AI Assistant works in the following way:
+
+1. Split our docs into smaller chunks
+2. Create an [embedding](#embeddings) for each chunk
+3. Save all these embeddings in [Postgres using pgvector (Supabase!)](https://supabase.com/docs/guides/database/extensions/pgvector)
+4. Get question from the user
+5. Create embedding for user’s question
+6. Perform a vector similarity search on your database — bring back all the chunks of your documentation that are similar to the user’s question
+7. Use the [GPT chat completion](https://platform.openai.com/docs/guides/text-generation/chat-completions-api) function. Pass a prompt, the user’s question and the retrieved chunks from the docs. GPT will then try to extract the relevant facts from these chunks, in order to formulate a coherent answer.
+
+This is based on the Web Q&A Tutorial from OpenAI [(https://platform.openai.com/docs/tutorials/web-qa-embeddings)](https://platform.openai.com/docs/tutorials/web-qa-embeddings) and Supabase’s Vector Search example [(https://supabase.com/docs/guides/ai/examples/nextjs-vector-search)](https://supabase.com/docs/guides/ai/examples/nextjs-vector-search).
+
+It’s important to note here that we are not “training the model on our docs”. The model is pretrained. We are just giving the model parts of our docs which are relevant to the user’s question, and the model creates a coherent answer to the question. It’s basically like pasting in ChatGPT a docs page and asking it “how do I do that?”. Except in this case, we’re first searching our documentation and giving GPT only the relevant parts (more about how we do that later in this article), which it can “read” and extract information from.
+
+## Step 1: Preprocessing our docs
+
+Every few days, we run an [automated script that will generate embeddings](https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/.github/workflows/generate-embeddings.yml) (numeric/vector representations of words and phrases) for our documentation, and store these embeddings in Supabase. As mentioned above, this step has 3 parts:
+
+### Split our docs into smaller chunks
+
+Most of this code follows the example from [Supabase’s Clippy](https://github.com/supabase-community/nextjs-openai-doc-search). It breaks the markdown tree into chunks, it keeps the heading and it also creates a checksum, to keep track of changes.
+
+Ref in the code: [https://github.com/nrwl/nx/blob/0197444df5ea906f38f06913b2bc366e04b0acc2/tools/documentation/create-embeddings/src/main.mts#L66](https://github.com/nrwl/nx/blob/0197444df5ea906f38f06913b2bc366e04b0acc2/tools/documentation/create-embeddings/src/main.mts#L66)
+
+This part is copied from: [https://github.com/supabase-community/nextjs-openai-doc-search/blob/main/lib/generate-embeddings.ts](https://github.com/supabase-community/nextjs-openai-doc-search/blob/main/lib/generate-embeddings.ts)
+
+```js
+export function processMdxForSearch(content: string) {
+  // …
+  const mdTree = fromMarkdown(content, {});
+  const sectionTrees = splitTreeBy(mdTree, (node) => node.type === 'heading');
+  // …
+  const sections = sectionTrees.map((tree: any) => {
+    const [firstNode] = tree.children;
+    const heading =
+      firstNode.type === 'heading' ? toString(firstNode) : undefined;
+    return {
+      content: toMarkdown(tree),
+      heading,
+      slug,
+    };
+  });
+  return {
+    checksum,
+    sections,
+  };
+}
+```
+
+### Create an embedding for each chunk
+
+Using `openai.embeddings.create` function with the model “text-embedding-ada-002” we are creating an embedding for each chunk.
+
+Ref in the code: [https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/tools/documentation/create-embeddings/src/main.mts#L314](https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/tools/documentation/create-embeddings/src/main.mts#L314)
+
+```js
+const embeddingResponse = await openai.embeddings.create({
+  model: 'text-embedding-ada-002',
+  input,
+});
+```
+
+### Save all these embeddings in Postgres using pgvector, on Supabase.
+
+Store this embedding in Supabase, in a database that has already been created, following the steps mentioned here:
+
+[https://supabase.com/docs/guides/ai/examples/nextjs-vector-search?database-method=dashboard#prepare-the-database](https://supabase.com/docs/guides/ai/examples/nextjs-vector-search?database-method=dashboard#prepare-the-database)
+
+Essentially, we are setting up two PostgreSQL tables on Supabase. Then, we are inserting the embeddings into these tables.
+
+Ref in code: [https://github.com/nrwl/nx/blob/master/tools/documentation/create-embeddings/src/main.mts#L327](https://github.com/nrwl/nx/blob/master/tools/documentation/create-embeddings/src/main.mts#L327)
+
+```js
+const { data: pageSection } = await supabaseClient
+  .from('nods_page_section')
+  .insert({
+    page_id: page.id,
+    slug,
+    heading,
+    longer_heading,
+    content,
+    url_partial,
+    token_count,
+    embedding,
+  }); // …
+```
+
+## Step 2: User query analysis and search
+
+When a user poses a question to the assistant, we calculate the embedding for the user’s question. The way we do that is, again, using openai.embeddings.create function with the model text-embedding-ada-002.
+
+Ref in code: [https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/nx-dev/nx-dev/pages/api/query-ai-handler.ts#L58](https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/nx-dev/nx-dev/pages/api/query-ai-handler.ts#L58)
+
+```js
+const embeddingResponse: OpenAI.Embeddings.CreateEmbeddingResponse =
+  await openai.embeddings.create({
+    model: 'text-embedding-ada-002',
+    input: sanitizedQuery + getLastAssistantMessageContent(messages),
+  });
+```
+
+The assistant compares the query embedding with these documentation embeddings to identify relevant sections. This comparison is essentially measuring how close the query’s vector is to the documentation vectors. The closer they are, the more related the content. The way this works is that it sends the user’s question embedding to Supabase, to a PostgreSQL function, which runs a vector comparison between the user’s question embedding and the stored embeddings in the table. The PostgreSQL function returns all the similar documentation chunks.
+
+The function that is used uses the dot product between vectors to calculate similarity. For normalized vectors, the dot product is equivalent to cosine similarity. Specifically, when two vectors A and B are normalized (i.e., their magnitudes are each 1), the cosine similarity between them is the same as their dot product. The OpenAI embeddings are normalized to length 1, so cosine similarity and dot product will produce the same results.
+
+Ref in code: [https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/nx-dev/nx-dev/pages/api/query-ai-handler.ts#L70](https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/nx-dev/nx-dev/pages/api/query-ai-handler.ts#L70)
+
+```js
+const { data: pageSections } = await supabaseClient.rpc('match_page_sections', {
+  embedding,
+  // …
+});
+```
+
+## Step 3: Generating a Response
+
+With the relevant sections (documentation chunks) identified and retrieved, GPT (the generative AI) steps in. Using the relevant sections as context and following a systematic approach, GPT crafts a response.
+
+This approach the AI is instructed to use (in the **prompt**) is the following:
+
+- Identify CLUES from the query and documentation.
+- Deduce REASONING based solely on the provided Nx Documentation.
+- EVALUATE its reasoning, ensuring alignment with Nx Documentation.
+- Rely on previous messages for contextual continuity.
+
+### Ensuring Quality
+
+If there’s no matching section in the documentation for a query, the script throws a “no_results” error. So, after the initial search in the docs (PostgreSQL function), if the search returns no results (no vectors found that are similar enough to the user’s question vector), the process stops, and our Assistant replies that it does not know the answer.
+
+### The use of useChat function
+
+It’s necessary here to clarify that we use the useChat [(https://sdk.vercel.ai/docs/api-reference/use-chat)](https://sdk.vercel.ai/docs/api-reference/use-chat) function of the [Vercel AI SDK](https://sdk.vercel.ai/docs/introduction). This function, as mentioned in the docs, does the following:
+
+> It enables the streaming of chat messages from your AI provider, manages the state for chat input, and updates the UI automatically as new messages are received.
+
+It essentially takes care of the following things:
+
+1. You don’t have to worry about manually creating a “messages” array to store your “conversation” (messages you exchange) with the GPT endpoint
+2. You don’t have to manually implement the streaming functionality in your UI
+
+Then, in your React component, you can call this function directly, and get the messages object from it, to render your messages in your UI. It exposes input, handleInputChange and handleSubmit which you can use in your React form, and it will take care of all the rest. You can pass an api string to it, to tell it which endpoint to use as the chat provider.
+
+### Creating the query
+
+If you look at our [query-ai-handler.ts](https://github.com/nrwl/nx/blob/76306f0bedc1297b64da6e58b4f7b9c39711cd82/nx-dev/nx-dev/pages/api/query-ai-handler.ts) function, this is an edge function, living under an endpoint, which is called by the useChat function. The request contains the messages array as created by useChat. If we just wanted to create an AI chat with no context, we could directly pass this messages array to the openai.chat.completions.create endpoint, and have our back-and-forth chat with GPT. However, in our case, we need to add context to our conversation, and specifically to each query we end up sending to OpenAI.
+
+So, the first thing we need to do is to **get the last message the user posted**, which is essentially the user’s question. We search the messages array, and we get the last message which has the role “user”. That is our user’s question.
+
+Now, we can use the user’s question to get the relevant documentation chunks from the database. To do that, as explained before, we need to **create an embedding for the user’s question** (a vector) and then compare that embedding with the stored embeddings in the database, to get the relevant chunks.
+
+The problem here is that if the user’s query is just a follow-up question, then it will have little information or meaning. Here is an example:
+
+> User: _How do I set up namedInputs?_
+> Assistant: _…replies…_
+> User: _And how do they work?_
+
+In this example, the user’s question that we would want to create an embedding for would be “And how do they work?”. If we created that embedding and searched our docs for relevant parts, it would either return nothing, or return everything, since this is a very vague question, since it has no context. So, we need to add some more information to that question. To do that, we also get the last response from GPT (the last assistant message) and add it to the user’s question. So, in this example, the user’s question will contain some info about namedInputs, and the actual question.
+
+Now, we take that combined text, and we create an embedding for it, using the openai.embeddings.create function. We, then, use that embedding to find all the similar documentation chunks, with vector similarity search.
+
+After receiving all the relevant documentation chunks, we can finally create the query that is going to be sent to GPT. It’s important here to make sure we instruct GPT what to do with the information we will give it.
+
+Here is the **query** we end up providing GPT with:
+
+> You will be provided sections of the Nx documentation in markdown format, use those to answer my question. Do NOT reveal this approach or the steps to the user. Only provide the answer. Start replying with the answer directly.
+>
+> Sections:
+> ${contextText}
+>
+> Question: “””
+> ${userQuestion}
+> “””
+>
+> Answer as markdown (including related code snippets if available):
+
+The contextText contains all the relevant documentation chunks (page sections).
+
+### Creating the response
+
+**Getting back a readable stream:** So, we get the array of messages, as stored by useChat, we fix the final message to contain the query (created as explained above), and we send it over to `openai.chat.completions.create`. We get back a streaming response (since we’ve set stream: true, which we turn into a ReadableStream using [OpenAIStream from the Vercel AI SDK](https://sdk.vercel.ai/docs/api-reference/openai-stream)).
+
+**Adding the sources:** However, we’re not done yet. The feature, here, that will be most useful to our users is the sources, the actual parts of the documentation that GPT “read” to create that response. When we get back the list of relevant documentation chunks (sections) from our database, we also get the metadata for each section. So, apart from the text content, we also get the heading and url partial of each section (among any other metadata we chose to save with it). So, with this information, we put together a list of the top 5 relevant sections, which we attach to the end of the response we get from GPT. That way, our users can more easily verify the information that GPT gives them, but also they can dive deeper into the relevant docs themselves. It’s all about exploring and retrieving relevant information, after all.
+
+**Sending the final response to the UI:** With the sources appended to the response, we return a StreamingTextResponse from our edge function, which the useChat function receives, and appends to the messages array automatically.
+
+## Allow user to reset the chat
+
+As explained, each question and answer relies on the previous questions and answers of the current chat. If a user needs to ask something completely irrelevant or different, we are giving the user the ability to do so by providing a “Clear chat” button, which will reset the chat history, and start clean.
+
+## Gathering feedback and evaluating the results
+
+It’s very important to gather feedback from the users and evaluate the results. Any AI assistant is going to give wrong answers, because it does not have the ability to critically evaluate the responses it creates. It relies on things it has read, but not in the way a human relies on them. It generates the next most probable word (see glossary for generative AI below). For that reason, it’s important to do the following things:
+
+1. Inform users that they should always double-check the answers and do not rely 100% on the AI responses
+2. Provide users with feedback buttons and/or a feedback form, where they can evaluate whether a response was good or bad. At Nx we do that, and we also associate each button click with the question the user asked, which will give us an idea around which questions the AI gets right or wrong.
+3. Have a list of questions that you ask the AI assistant, and evaluate its responses internally. Use these questions as a standard for any changes made in the assistant.
+
+## Wrapping up
+
+In this guide, we’ve explored the intricacies of the Nx Docs AI Assistant, an innovative tool that enhances the experience of both users and authors of Nx documentation. From understanding the need for an AI assistant in navigating complex documentation to the detailed workflow of the Nx Docs AI Assistant, we have covered the journey from preprocessing documentation to generating coherent and context-aware responses.
+
+Let’s see at some key takeaways:
+
+**Enhanced User Experience:** The AI assistant significantly improves user interaction with documentation by offering personalized, context-aware responses to queries. This not only makes information retrieval more efficient but also elevates the overall user experience.
+
+**Insights for Authors:** By analyzing frequently asked questions and areas where the AI struggles, authors can pinpoint documentation gaps and areas for improvement, ensuring that the Nx documentation is as clear and comprehensive as possible.
+
+**OpenAI API utilization:** The use of embeddings, vector similarity search, and GPT’s generative AI capabilities demonstrate a sophisticated approach to AI-driven documentation assistance. This blend of technologies ensures that users receive accurate and relevant responses.
+
+**Continuous Learning and Improvement:** The system’s design includes mechanisms for gathering user feedback and evaluating AI responses, which are crucial for ongoing refinement and enhancement of the assistant’s capabilities.
+
+**Transparency and User Trust:** By openly communicating the limitations of the AI and encouraging users to verify the information, the system fosters trust and promotes responsible use of AI technology.
+
+**Accessibility and Efficiency:** The AI assistant makes Nx documentation more accessible and navigable, especially for complex or nuanced queries, thereby saving time and enhancing productivity and developer experience.
+
+## Future steps
+
+OpenAI released the Assistants API, which takes the burden of chunking the docs, creating embeddings, storing the docs in a vector database, and querying that database off the shoulders of the developers. This new API offers all these features out of the box, removing the need to create a customized solution, as the one explained above. It’s still in beta, and it remains to be seen how it’s going to evolve, and if it’s going to overcome some burdens it poses at the moment. You can [read more about the new Assistants API in this blog post](https://pakotinia.medium.com/openais-assistants-api-a-hands-on-demo-110a861cf2d0), which contains a detailed demo on how to use it for documentation q&a.
+
+## Glossary
+
+### Core concepts
+
+I find it useful to start by explaining what some terms — which are going to be used quite a lot throughout this blog post — mean.
+
+### Embeddings
+
+#### What they are
+
+In the context of machine learning, embeddings are a type of representation for text data. Instead of treating words as mere strings of characters, embeddings transform them into **vectors** (lists of numbers) in a way that captures their meanings. In embeddings, vectors are like digital fingerprints for words or phrases, converting their essence into a series of numbers that can be easily analyzed and compared.
+
+#### Why they matter
+
+With embeddings, words or phrases with similar meanings end up having **vectors** that are close to each other, making it easier to compare and identify related content.
+
+### Generative AI
+
+#### What it is
+
+Generative AI, the technology driving the Nx Docs AI Assistant, is a subset of AI that’s trained, not just to classify input data, but to generate new content.
+
+#### How it works
+
+Generative AI operates like a sophisticated software compiler. Just as a compiler takes in high-level code and translates it into machine instructions, generative AI takes in textual prompts and processes them through layers of neural network operations, resulting in detailed and coherent text outputs. It’s like providing a programmer with a high-level task description, and they write the necessary code to achieve it, except here the ‘programmer’ is the AI, and the ‘code’ is the generated text response.
+
+#### What Does “Generation” Mean in AI Context?
+
+In AI, especially with natural language processing models, “generation” refers to the process of producing sequences of data, in our case, text. It’s about creating content that wasn’t explicitly in the training data but follows the same patterns and structures.
+
+#### How Does GPT Predict the Next Word?
+
+For our Nx Docs AI assistant we use GPT. GPT, which stands for “Generative Pre-trained Transformer”, works using a predictive mechanism. At its core, it’s trained to predict the next word in a sentence. When you provide GPT with a prompt, it uses that as a starting point and keeps predicting the next word until it completes the response or reaches a set limit.
+
+It’s like reading a sentence and trying to guess the next word based on what you’ve read so far. GPT does this but by using a massive amount of textual data it has seen during training, enabling it to make highly informed predictions.
+
+### Context and Prompting — their role in AI models
+
+#### Context
+
+In the context of AI, “context” refers to the surrounding information, data, or conditions that provide a framework or background for understanding and interpreting a specific input, ensuring that the AI’s responses or actions are relevant, coherent, and meaningful in a given situation
+
+#### Prompts
+
+The prompt acts as an initial “seed” that guides the AI’s output. While the AI is trained on vast amounts of text, it relies on the prompt for context. For example, a prompt like “tell me about cats” might result in a broad answer, but “summarize the history of domesticated cats” narrows the model’s focus.
+
+By refining prompts, users can better direct the AI’s response, ensuring the output matches their intent. In essence, the prompt is a tool to direct the AI’s vast capabilities to a desired outcome.
+
+### The GPT Chat Completion Roles
+
+### System
+
+The “System” role typically sets the “persona” or the “character” of the AI. It gives high-level instructions on how the model should behave during the conversation. We start the instructions with “You are a knowledgeable Nx representative.” We also instruct the model about the format of its answer: “Your answer should be in the form of a Markdown article”. You can read the full instructions on GitHub.
+
+#### User
+
+The “User” role is straightforward. This is the input from the end-user, which the AI responds to. The user’s query becomes the User role message. This role guides what the AI should be talking about in its response. It’s a direct prompt to the AI to generate a specific answer. In our case, we take the user’s query, and we add it in a longer prompt, which specific steps the model must follow (as explained above). That way, the model focuses on the specific steps we’ve laid out, making it the immediate context for generating the answer. This is one more step towards more accurate answers based on our documentation only. Inside the prompt, which has the instructions, and the user’s query, we always add the context text as well, which are the relevant parts that are retrieved from the Nx Documentation.
+
+#### Assistant
+
+This role, in the context of OpenAI’s chat models, is the response of the AI. Previous Assistant responses can be included in the chat history to provide context, especially if a conversation has back-and-forth elements. This helps the model generate coherent and contextually relevant responses in a multi-turn conversation.
+
+---
+
+## Learn more
+
+- [Nx Docs](/getting-started/intro)
+- [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
+- [Nx GitHub](https://github.com/nrwl/nx)
+- [Nx Official Discord Server](/community)
+- [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
+- [Speed up your CI](https://nx.app/)
@@ -1,5 +1,6 @@
 ---
 title: Unit Testing Expo Apps With Jest
+slug: 'unit-testing-expo-apps-with-jest'
 authors: [Emily Xiong]
 cover_image: '/blog/images/2023-11-22/featured_img.webp'
 tags: [nx, unit testing]
@@ -330,6 +331,6 @@ With Nx, you do not need to explicitly install any testing library, so you can d
 - [Add Cypress, Playwright, and Storybook to Nx Expo Apps](https://medium.com/@emilyxiong/add-cypress-playwright-and-storybook-to-nx-expo-apps-1d3e409ce834)
 - 🧠 [Nx Docs](/getting-started/intro)
 - 👩‍💻 [Nx GitHub](https://github.com/nrwl/nx)
- 💬 [Nx Community Discord](/community)
+- 💬 [Nx Community Discord](https://go.nx.dev/community)
 - 📹 [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - 🚀 [Speed up your CI](https://nx.app/)
@@ -1,11 +1,12 @@
 ---
 title: Nx 17.2 Update
+slug: 'nx-17-2-release'
 authors: [Zack DeRose]
 cover_image: '/blog/images/2023-12-20/featured_img.png'
 tags: [nx, changelog, release]
 ---

-It’s been a bit since we launched [Nx 17](/blog/2023-10-20-nx-17-release)! In this article, we’ll go over some of the new developments and improvements that have landed in Nx 17.2:
+It’s been a bit since we launched [Nx 17](/blog/nx-17-release)! In this article, we’ll go over some of the new developments and improvements that have landed in Nx 17.2:

 - [Nx Closes In On 4 Million Weekly NPM Downloads!!](#nx-closes-in-on-4-million-weekly-npm-downloads)
 - [New Simplified Project Configuration On the Way](#new-simplified-project-configuration-on-the-way)
@@ -109,7 +110,7 @@ nx release version patch --project=my-project

 ![](/blog/images/2023-12-20/bodyimg2.webp)

-[Angular](https://angular.dev/) is in the middle of [a HUGE renaissance](https://blog.angular.io/introducing-angular-v17-4d7033312e4b), between their new logo, new docs site, and introduction of some awesome features like Signals.
+[Angular](https://angular.dev/) is in the middle of [a HUGE renaissance](https://blog.angular.dev/introducing-angular-v17-4d7033312e4b), between their new logo, new docs site, and introduction of some awesome features like Signals.

 Nx is here to support the transition! Nx has always been a great fit for Angular, and now supports Angular 17 as well as NgRx 17.

@@ -209,6 +210,6 @@ That’s all for now folks! We’re just starting up a new iteration of developm
 - [Nx Docs](/getting-started/intro)
 - [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,5 +1,6 @@
 ---
 title: Nx — Highlights of 2023
+slug: 'nx-highlights-of-2023'
 authors: [Juri Strumpflohner, Victor Savkin, Zack DeRose]
 cover_image: /blog/images/2023-12-28/featured_img.png
 tags: [nx, nx-cloud]
@@ -94,7 +95,7 @@ Nx Console has evolved from an experimental side project of the Nx team to a cor

 ![](/blog/images/2023-12-28/bodyimg2.webp)

-This year we not only added a lot of new features to Nx Console, but also rewrote its [internals](https://blog.nrwl.io/nx-console-gets-lit-ca339743ff4f) which paved the way to expand Nx Console to other code editors: **JetBrains IDEs.**
+This year we not only added a lot of new features to Nx Console, but also rewrote its [internals](/blog/nx-console-gets-lit) which paved the way to expand Nx Console to other code editors: **JetBrains IDEs.**

 Yes, this means you can now use the latest Nx Console directly in your [Webstorm IDE](https://www.jetbrains.com/webstorm/). Read the [announcement blog post](https://blog.nrwl.io/expanding-nx-console-to-jetbrains-ides-8a5b80fff2d7) for all the details or go ahead and install Nx Console if you didn’t already:

@@ -328,7 +329,7 @@ You can also browse them in the [nx-recipes](https://github.com/nrwl/nx-recipes)

 {% tweet url="https://twitter.com/juristr/status/1726977598218199302" /%}

-And obviously, we jumped on the AI train as well. A couple of months ago, we added the [Nx Assistant](/ai-chat). A ChatGPT-powered interface trained on our docs. [Katerina](https://twitter.com/psybercity) wrote about it [on our blog](https://blog.nrwl.io/nx-docs-ai-assistant-433d238e45d4). The AI chat allows to interactively ask questions about Nx and will give you relevant answers from our docs (including linking to the sources).
+And obviously, we jumped on the AI train as well. A couple of months ago, we added the [Nx Assistant](/ai-chat). A ChatGPT-powered interface trained on our docs. [Katerina](https://twitter.com/psybercity) wrote about it [on our blog](/blog/nx-docs-ai-assistant). The AI chat allows to interactively ask questions about Nx and will give you relevant answers from our docs (including linking to the sources).

 ## New Tagline: Smart Monorepos — Fast CI

@@ -348,7 +349,7 @@ We did it again! The second in-person Nx Conf was a resounding success, this tim

 ![](/blog/images/2023-12-28/bodyimg9.webp)

-There’s not much to say. Check out some of the amazing talks. I did a [Nx Conf 2023 recap blog post](https://dev.to/nx/nx-conf-2023-recap-53ep).
+There’s not much to say. Check out some of the amazing talks. I did a [Nx Conf 2023 recap blog post](/blog/nx-conf-2023-recap).

 ## Looking ahead — 2024

@@ -1,5 +1,6 @@
 ---
 title: What if Nx Plugins Were More Like VSCode Extensions
+slug: 'what-if-nx-plugins-were-more-like-vscode-extensions'
 authors: [Juri Strumpflohner]
 cover_image: '/blog/images/2024-02-05/featured_img.png'
 tags: [nx, releases]
@@ -182,6 +183,6 @@ We just released Project Crystal, so this is just the beginning of it. While we

 - [Nx Docs](/getting-started/intro)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,5 +1,6 @@
 ---
 title: Introducing @nx/nuxt Enhanced Nuxt.js Support in Nx
+slug: 'introducing-nx-nuxt-enhanced-nuxt-js-support-in-nx'
 cover_image: '/blog/images/2024-02-06/featured_img.png'
 authors: ['Katerina Skroumpelou']
 tags: [devtools, javascript, monorepos, nuxt]
@@ -184,6 +185,6 @@ Whether you're starting a new Nuxt project or looking to enhance an existing one
 - [Nx Docs](/getting-started/intro)
 - [X / Twitter](https://twitter.com/nxdevtools) - [LinkedIn](https://www.linkedin.com/company/nrwl)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Community Discord](/community)
+- [Nx Community Discord](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app)
@@ -1,5 +1,6 @@
 ---
 title: Fast, Effortless CI
+slug: 'fast-effortless-ci'
 authors: [Isaac Mann]
 cover_image: '/blog/images/2024-02-07/featured_img.png'
 tags: [nx, nx-cloud, release]
@@ -101,7 +102,7 @@ Nx understands that some CI pipelines need more resources than others. To accoun

 ## Automatically Split E2E Tasks by File

-Typically, e2e tests are the tasks that take the longest in CI. In order to take advantage of parallelization and task distribution, these large tasks would need to be split into smaller tasks, but doing this manually would involve duplicating a lot of configuration code and making sure to keep that configuration synchronized. Nx 18’s [Project Crystal](/blog/2024-02-05-nx-18-project-crystal) allows you to [automatically create separate Cypress and Playwright tasks](/ci/features/split-e2e-tasks) for each spec file in the e2e project. These individual tasks can all be triggered by running the `e2e-ci` task. What was once a tedious manual process can now be done for you automatically.
+Typically, e2e tests are the tasks that take the longest in CI. In order to take advantage of parallelization and task distribution, these large tasks would need to be split into smaller tasks, but doing this manually would involve duplicating a lot of configuration code and making sure to keep that configuration synchronized. Nx 18’s [Project Crystal](/blog/what-if-nx-plugins-were-more-like-vscode-extensions) allows you to [automatically create separate Cypress and Playwright tasks](/ci/features/split-e2e-tasks) for each spec file in the e2e project. These individual tasks can all be triggered by running the `e2e-ci` task. What was once a tedious manual process can now be done for you automatically.

 ![](/blog/images/2024-02-07/bodyimg3.webp)

@@ -121,6 +122,6 @@ If you have a task that can’t be run on Nx Agents for some reason, you can eas

 - [Nx Docs](/getting-started/intro)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,5 +1,6 @@
 ---
 title: Versioning and Releasing Packages in a Monorepo
+slug: 'versioning-and-releasing-packages-in-a-monorepo'
 authors: [Juri Strumpflohner]
 cover_image: '/blog/images/2024-02-09/featured_img.png'
 tags: [nx, nx-cloud, releases, changelog]
@@ -48,11 +49,11 @@ pnpm dlx nx@latest init

 (use `npx nx@latest init` in a NPM workspace)

-This brings up a couple of questions including whether to install [Project Crystal plugins](/blog/2024-02-05-nx-18-project-crystal).
+This brings up a couple of questions including whether to install [Project Crystal plugins](/blog/what-if-nx-plugins-were-more-like-vscode-extensions).

 ![](/blog/images/2024-02-09/bodyimg2.webp)

-It gives you some additional benefits ([you can read more here](/blog/2024-02-05-nx-18-project-crystal)), but you don’t have to as it is not required for Nx Release.
+It gives you some additional benefits ([you can read more here](/blog/what-if-nx-plugins-were-more-like-vscode-extensions)), but you don’t have to as it is not required for Nx Release.

 ## Installing the JavaScript/TypeScript versioning Package

@@ -1,5 +1,6 @@
 ---
 title: Launch Nx Week Recap
+slug: 'launch-nx-week-recap'
 authors: [Zack DeRose]
 cover_image: '/blog/images/2024-02-15/featured_img.png'
 tags: [nx, nx-cloud, releases, changelog]
@@ -36,7 +37,7 @@ Juri announced launched Project Crystal with this video:

 The short version is: Nx project crystal means Nx plugins make your codebases work more seemlessly with less config.

-For the long version, checkout this blog post by Juri where he describes [how Nx plugins are now more like VsCode Extentions](/blog/2024-02-05-nx-18-project-crystal)!
+For the long version, checkout this blog post by Juri where he describes [how Nx plugins are now more like VsCode Extentions](/blog/what-if-nx-plugins-were-more-like-vscode-extensions)!

 And don’t miss our two conference talks on this subject:

@@ -80,7 +81,7 @@ We’re very excited about Nx Agents because we think that in its current state,

 {% youtube src="https://www.youtube.com/embed/_FSHQIwITic?si=jDpwTVXLYFXiHEm0" title="Nx Agents" /%}

-Be sure to also checkout the [blog post from Isaac on Nx Agents](/blog/2024-02-07-fast-effortless-ci), including explanations of exclusive features like auto-detection and retrying for flaky tasks and automatically splitting lengthy end-to-end tests!
+Be sure to also checkout the [blog post from Isaac on Nx Agents](/blog/fast-effortless-ci), including explanations of exclusive features like auto-detection and retrying for flaky tasks and automatically splitting lengthy end-to-end tests!

 You can [signup for Nx Agents NOW](https://nx.app/products/agents#content), and find out [more of the details in our docs](/ci/features/distribute-task-execution)!

@@ -120,7 +121,7 @@ For a long time, Nx has been purposefully versioning and publishing agnostic, bu

 Therefore, we’ve been working on a new command to the Nx CLI: [nx release](/recipes/nx-release/get-started-with-nx-release#get-started-with-nx-release). We launched this on Friday of our Launch Nx week!

-Juri goes into [full details in this blog post](/blog/2024-02-09-versioning-and-releasing-packages), and James Henry — our Director of Engineering and the primary engineer responsible for both maintaining Lerna and creating Nx Release — expands further in his conference talk:
+Juri goes into [full details in this blog post](/blog/versioning-and-releasing-packages-in-a-monorepo), and James Henry — our Director of Engineering and the primary engineer responsible for both maintaining Lerna and creating Nx Release — expands further in his conference talk:

 ### Conference Talk: Releasing Nx Release

@@ -142,6 +143,6 @@ That’s all for now folks! We’re just starting up a new iteration of developm

 - [Nx Docs](/getting-started/intro)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,7 +1,8 @@
 ---
 title: Monorepos - Why Speed Matters
-authors: ['Katerina Skroumpelou']
-tags: nx, nxdevtools, speed, ci
+slug: 'monorepos-why-speed-matters'
+authors: ['Katerina Skroumpelou', 'Jeff Cross']
+tags: [nx, nxdevtools, speed, ci]
 cover_image: '/blog/images/2024-03-20/featured_img.png'
 ---

@@ -99,6 +100,6 @@ Nx provides an unparalleled toolkit for developers and teams looking to optimize
 - [X / Twitter](https://twitter.com/nxdevtools)
 - [LinkedIn](https://www.linkedin.com/company/nrwl)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Community Discord](/community)
+- [Nx Community Discord](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app)
@@ -1,5 +1,6 @@
 ---
 title: Reliable CI. A new execution model fixing both flakiness and slowness
+slug: 'reliable-ci-a-new-execution-model-fixing-both-flakiness-and-slowness'
 authors: [Victor Savkin]
 cover_image: '/blog/images/2024-03-21/featured_img.png'
 tags: [nx, nx-cloud, releases]
@@ -102,7 +103,7 @@ Nx Cloud introduces an entirely different model. Instead of the graph of VMs, th
 By adding the following line…

 ```shell
-npx nx-cloud start-ci-run --distribute-on="5 linux-medium-js"
+npx nx-cloud start-ci-run --distribute-on="3 linux-medium-js"
 ```

 ... you are telling Nx Cloud to create five Nx Agents to execute all the tasks from all the commands that will follow.
@@ -174,3 +175,15 @@ You can learn more about Nx Cloud on [nx.app](https://nx.app) and Nx open source
 **Nx Cloud Pro includes a 2-month free trial** that is definitely worth trying out if you're curious what Cloud Pro can do for your CI. You can try out Nx Agents, e2e test splitting, deflaking and more. [Learn more about Nx Cloud Pro.](https://nx.app/campaigns/pro)

 We also have a **Pro for Startups** plan which offers agents that are 3.5x cheaper than analogous VMs on CircleCI or Github Actions. [Learn more about Nx Pro for Startups.](https://nx.app/campaigns/pro-for-startups)
+
+---
+
+## Learn more
+
+- [Nx Docs](/getting-started/intro)
+- [X / Twitter](https://twitter.com/nxdevtools)
+- [LinkedIn](https://www.linkedin.com/company/nrwl)
+- [Nx GitHub](https://github.com/nrwl/nx)
+- [Nx Community Discord](https://go.nx.dev/community)
+- [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
+- [Speed up your CI](https://nx.app)
@@ -1,5 +1,6 @@
 ---
 title: Manage Your Gradle Project using Nx
+slug: 'manage-your-gradle-project-using-nx'
 authors: ['Emily Xiong']
 cover_image: '/blog/images/2024-04-19/featured_img.png'
 tags: [nx, gradle, how-to]
@@ -212,6 +213,6 @@ Here is how to set up Nx with the Gradle workspace. Hopefully, this gives you a
 - [Nx Docs](/getting-started/intro)
 - [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -1,22 +1,18 @@
 ---
 title: Nx 19.0 Release!!
+slug: 'nx-19-release'
 authors: ['Zack DeRose']
 cover_image: '/blog/images/2024-05-08/nx-19-thumbnail.png'
 tags: [nx, release]
 ---

-{% youtube
-src="https://youtu.be/U6eO8-w9DR0"
-title="Nx 19.0 Has Landed!!"
-width="100%" /%}
-
 Hey folks!

 It's been awhile since February, where in the midsts our big launch week, we launched Nx 18. Nx 18 introduced the biggest new enhancement to Nx to date: Project Crystal.

-[![Project Crystal](/blog/images/2024-02-05/featured_img.png)](/blog/2024-02-05-nx-18-project-crystal)
+[![Project Crystal](/blog/images/2024-02-05/featured_img.png)](/blog/what-if-nx-plugins-were-more-like-vscode-extensions)

-You can read more on project crystal [here](/blog/2024-02-05-nx-18-project-crystal). The main thing to know though is that Project Crystal adjusts the idea of Nx plugins, so that the mere presence of the plugin in your Nx Workspace removes the need to maintain any configuration for most cases.
+You can read more on project crystal [here](/blog/what-if-nx-plugins-were-more-like-vscode-extensions). The main thing to know though is that Project Crystal adjusts the idea of Nx plugins, so that the mere presence of the plugin in your Nx Workspace removes the need to maintain any configuration for most cases.

 Nx 18 was a significant departure for us in several ways - maybe the most noteworthy was that we broke our years-long cadence of releasing a new major version every 6 months.

@@ -36,13 +32,22 @@ Here's the rundown of the major things we'll cover in this update:
 - [Wrapping Up, And A Heartfelt Thank You](#wrapping-up-and-a-heartfelt-thank-you)
 - [Learn More](#learn-more)

+**Prefer a video?**
+
+{% youtube
+src="https://youtu.be/U6eO8-w9DR0"
+title="Nx 19.0 Has Landed!!"
+width="100%" /%}
+
+---
+
 ## NEW PLUGIN: @nx/gradle

-[![NEW PLUGIN: @nx/gradle](/blog/images/2024-04-19/featured_img.png)](/blog/2024-04-19-manage-your-gradle)
+[![NEW PLUGIN: @nx/gradle](/blog/images/2024-04-19/featured_img.png)](/blog/manage-your-gradle-project-using-nx)

 We've launched a new first-party plugin for Gradle!

-Emily, the engineer that worked on this effort, posted an entire article where you can find the full details [here](/blog/2024-04-19-manage-your-gradle).
+Emily, the engineer that worked on this effort, posted an entire article where you can find the full details [here](/blog/manage-your-gradle-project-using-nx).

 Thanks to the benefits of Project Crystal - which allows us to determine information to create Nx Tasks based on the way your Gradle projects are setup - by adding this plugin, it makes it easy to add Gradle into an existing workspace without needing any Nx-specific configuration.

@@ -77,7 +82,7 @@ Notice how all tasks are now appropriately grouped in the `E2E (CI)` group!

 You can also find the same enhancements in Nx Cloud. Below is a view of all tasks in the [CI pipeline](https://staging.nx.app/runs/ctbAZfiLy3):

-[![Grouped e2e tests in Nx Cloud](/blog/images/2024-05-08/nx-cloud-atomizer-groupings.gif)](https://staging.nx.app/runs/ctbAZfiLy3)
+{% video-player src="/documentation/blog/media/2024-05-08/nx-cloud-atomizer-groupings.mp4" alt="Showing the Atomizer in Nx Cloud" link="https://staging.nx.app/runs/ctbAZfiLy3" /%}

 Notice how all e2e groups are collapsed by default to give a concise view, while allowing you to expand to see how each individual task is progressing!

@@ -155,7 +160,7 @@ Since Nx 18 release, we also started using Project Crystal inside of the Nx repo

 You can find a full list of fixes and features applied in this major release [here](https://github.com/nrwl/nx/releases/tag/19.0.0).

-[![Changelog for Nx 19](/blog/images/2024-05-08/fixes.gif)](https://github.com/nrwl/nx/releases/tag/19.0.0)
+{% video-player src="/documentation/blog/media/2024-05-08/fixes.mp4" alt="A display listing the Github changelog" /%}

 With Project Crystal landed now, we're also adjusting our priorities to place a higher importance on stability. You should see this reflected in Nx 19.

@@ -171,13 +176,13 @@ We've got some cool stats to share from our users regarding the benefits of [Nx

 - **speed**: Reported 30% - 70% faster CI
 - **cost**: Reported 40% - 75% reduction in CI costs
- **reliability**: Nx Cloud's automatic detection and retrying of flaky tests makes the issue of flaky tests largely go away entirely. You can read more on [our thoughts on reliability here](/blog/2024-03-21-reliable-ci).
+- **reliability**: Nx Cloud's automatic detection and retrying of flaky tests makes the issue of flaky tests largely go away entirely. You can read more on [our thoughts on reliability here](/blog/reliable-ci-a-new-execution-model-fixing-both-flakiness-and-slowness).

 In February, we launched two big enhancements to Nx Cloud: the [Atomizer](/ci/features/split-e2e-tasks) and [Nx Agents](https://nx.app/products/agents#content).

 Since then, the Atomizer has received a nice UI update (as we had seen earlier):

-[![Grouped e2e tests in Nx Cloud](/blog/images/2024-05-08/nx-cloud-atomizer-groupings.gif)](https://staging.nx.app/runs/ctbAZfiLy3)
+{% video-player src="/documentation/blog/media/2024-05-08/nx-cloud-atomizer-groupings.mp4" alt="Showing the Atomizer in Nx Cloud" link="https://staging.nx.app/runs/ctbAZfiLy3" /%}

 Since February, we also revamped our task distribution algorithms. This has resulted in a 5-20% (depending on the repo) increase in both speed and cost efficiency for our users.

@@ -195,9 +200,9 @@ And! We've revamped our newsletter, written by our CTO, Victor Savkin. [Subscrib

 ## NEW CONFERENCE: Monorepo World 2024

-[![NEW CONFERENCE: Monorepo World 2024](/blog/images/2024-05-08/welcome-to-monorepo-world-2024.webp)](https://monorepo.tools/conf)
+[![NEW CONFERENCE: Monorepo World 2024](/blog/images/2024-05-08/welcome-to-monorepo-world-2024.webp)](https://monorepo.world)

-We've got a new conference coming up: [Monorepo World 2024](https://monorepo.tools/conf)!
+We've got a new conference coming up: [Monorepo World 2024](https://monorepo.world)!

 This conference will cover all things dealing with monorepos, and we're excited to host it at the Computer History Museum in Mountain View, California this October 7th!

@@ -228,6 +233,6 @@ Zack
 - [Nx Docs](/getting-started/intro)
 - [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
 - [Nx GitHub](https://github.com/nrwl/nx)
- [Nx Official Discord Server](/community)
+- [Nx Official Discord Server](https://go.nx.dev/community)
 - [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
 - [Speed up your CI](https://nx.app/)
@@ -0,0 +1,176 @@
+---
+title: 'Nx 19.5: StackBlitz, New Features, And More!!'
+slug: 'nx-19-5-adds-stackblitz-new-features-and-more'
+authors: ['Zack DeRose']
+cover_image: '/blog/images/2024-07-25/nx-19-5-thumbnail.png'
+tags: [nx, release]
+---
+
+## Table of Contents
+
+In this blog post:
+
+- [StackBlitz Support](#stackblitz-support)
+- [NEW: Pattern Support for `targetDefaults`](#new-pattern-support-for-targetdefaults)
+- [NEW: Individual Targets Can Now Opt Out of Parallelism](#new-individual-targets-can-now-opt-out-of-parallelism)
+- [Experimental: Gradle Test Atomization](#experimental-gradle-test-atomization)
+- [Support for React 19 (rc) and Angular 18.1](#support-for-react-19-rc-and-angular-181)
+- [NEW: Nx Cloud Hobby Tier](#new-nx-cloud-hobby-tier)
+- [Automatically Update Nx](#automatically-update-nx)
+- [Monorepo World Conference Speakers to Be Announced Soon!!](#monorepo-world-conference-speakers-to-be-announced-soon)
+
+## StackBlitz Support!!
+
+Nx now has support for Stackblitz. This means that you can create a StackBlitz with a whole Nx Workspace inside of it and run all Nx capabilities from their embedded terminal.
+
+[![Nx Workspace in Stackblitz](/blog/images/2024-07-25/react-app-in-stackblitz.jpg)](https://stackblitz.com/edit/stackblitz-webcontainer-api-starter-cwruaw?file=apps%2Freact-app%2Fsrc%2Fapp%2Fapp.tsx)
+
+[Check out the example](https://stackblitz.com/edit/stackblitz-webcontainer-api-starter-cwruaw?file=apps%2Freact-app%2Fsrc%2Fapp%2Fapp.tsx) above - you can use the standard command in the terminal:
+
+```shell
+> nx serve react-app
+```
+
+to develop your application inside of the stackblitz.
+
+We're excited for this as it opens up many interesting use-cases, including easier ways of sharing examples, better opportunities for reproduction of issues or bugs, and potential for us to use embedded examples in our documentation in the future.
+
+Web Assembly (or WASM) is the underlying technology being used here, so in addition to stackblitz any other tools built on a node context should now work as well.
+
+## NEW: Pattern Support for `targetDefaults`
+
+When using the Atomizer features of plugins like [`@nx/playwright`](/nx-api/playwright) and [`@nx/cypress`](/nx-api/cypress), you end up creating tasks with dynamic but predictable names.
+
+![Tasks Created With Atomizer](/blog/images/2024-07-25/e2e-task-names.jpg)
+
+Notice how the `e2e-ci--src/example.spec.ts` and `e2e-ci--src/test.spec.ts` tasks here are created by the `@nx/playwright` plugin based on the playwright spec files present in your workspace.
+
+We've now added pattern matching to `targetDefaults` task names as a way to target these dynamic tasks.
+
+The following will set all such tasks to depend on their `build` task:
+
+```json
+{
+  "targetDefaults": {
+    "e2e-ci--**/*": {
+      "dependsOn": ["build"]
+    }
+  }
+}
+```
+
+Note that our plugins will set sensible configurations here out of the box when creating new workspaces using our generators.
+
+Read more about [reducing configuration with `targetDefaults`](/recipes/running-tasks/reduce-repetitive-configuration#reduce-configuration-with-targetdefaults) and [how you can define task pipelines with `targetDefaults`](/features/run-tasks#defining-a-task-pipeline).
+
+## NEW: Individual Targets Can Now Opt Out of Parallelism
+
+One of our goals in changing the landscape of CI is to make CI more declarative - defining the what rather than the how.
+
+Unfortunately, to accomodate for port collisions on end-to-end test, we've long adjusted our generated ci script to look like this:
+
+```yml
+- run: npx nx affected -t lint test build
+- run: npx nx affected --parallel 1 -t e2e-ci
+```
+
+This is unfortunately more imperative, as we are starting to give instructions on how to run and order your CI, rather than defining what to run in our CI. In addition, these instructions will still run `lint`, `test`, and `build` targets first and wait until they all complete before then running `e2e-ci` - which leaves some inefficiencies on the table.
+
+To address this, all tasks now support a `parallelism` property. By setting this property to `false`, you can now inform the Nx task runner to not attempt to run a certain task in parallel. This way we can define parallelism as a property of a task, and move our task running to be more declarative again.
+
+Both our `@nx/playwright` and `@nx/cypress` plugins will now set `targetDefaults` for atomized tests to turn off `parallelism` from now on:
+
+```json
+{
+  // ...
+  "targetDefaults": {
+    "e2e-**/*": {
+      // ...
+      "parallelism": false
+    }
+  }
+}
+```
+
+This way we can simply run the command:
+
+```shell
+> nx run-many --targets=lint,test,e2e-ci,build
+```
+
+And in CI, Nx Agents will allow all tasks to run in parallel on the same machine, except for the atomized end-to-end tasks, which will only run in isolation.
+
+Learn more about how you can [Parallelize Tasks Across Multiple Machines Using Nx Agents](/ci/intro/tutorials/github-actions#parallelize-tasks-across-multiple-machines-using-nx-agents):
+
+{% youtube
+src="https://youtu.be/0YxcxIR7QU0"
+title="Faster e2e Tests!"
+width="100%" /%}
+
+## Experimental: Gradle Test Atomization
+
+Our new [`@nx/gradle` plugin](/nx-api/gradle) now supports Test Atomization out of the box.
+
+![Gradle Atomized](/blog/images/2024-07-25/gradle-atomized.jpg)
+
+This means that as you add tests in your gradle projects, we'll automatically create a new task for each test class, allowing you to distribute the execution of these tasks in your CI pipeline, just like with our `@nx/playwright` and `@nx/cypress` plugins.
+
+## Support for React 19 (rc) and Angular 18.1
+
+Nx 19.5 adds support for the React 19 release candidate and updated our Angular package to support the latest Angular minor version: 18.1.
+
+When using our `@nx/angular` package, we'll automatically update you to the latest angular version when you run our migration. Using the `--interactive` flag you can choose to opt in or out of the latest Angular version:
+
+```shell
+> nx migrate latest --interactive
+✔ Do you want to update to TypeScript v5.5? (Y/n) · true
+✔ Do you want to update the Angular version to v18.1? (Y/n) · true
+Fetching @angular/core@18.1.2
+
+ NX   The migrate command has run successfully.
+```
+
+Our `@nx/react` package will now create new React applications using version 18.3, and we now support the new experimental `reactCompiler`. Users can install the [`babel-plugin-react-compiler` package](https://www.npmjs.com/package/babel-plugin-react-compiler) and you can follow [this guide for how to enable it with Nx](/recipes/react/react-compiler#react-compiler-with-nx).
+
+Note that due to the extent of breaking changes coming with React 19, we will not be providing a automated migration to React 19 via [`nx migrate`](/nx-api/nx/documents/migrate).
+
+## Automatically Update Nx
+
+As always - updating Nx and its plugins is easy as we ship an [automated migration command](/features/automate-updating-dependencies).
+
+```shell
+npx nx migrate latest
+```
+
+After updating your dependencies, run any necessary migrations.
+
+```shell
+npx nx migrate --run-migrations
+```
+
+## NEW: Nx Cloud Hobby Tier
+
+Our new expanded Hobby Tier now adds trial support for all features AND includes credits to run Nx Agents.
+
+Sample the entire suite of features to see its impact on your organization. Start with everything, scale when you need more.
+
+[![Nx Cloud Tiers](/blog/images/2024-07-25/start-with-everything-scale-when-you-need.jpg)](https://nx.app/pricing#plan-details)
+
+Checkout the [plan details page](https://nx.app/pricing#plan-details) for more info, and see how Nx Cloud can help you!
+
+## Monorepo World Conference Speakers to Be Announced Soon!!
+
+[![Monorepo World](/blog/images/2024-07-25/monorepo-world.jpg)](https://monorepo.world)
+
+The [Monorepo World conference](https://monorepo.world) is coming up soon on October 7, 2024 at the Computer History museum in Mountain View, California.
+
+[Get your tickets now](https://ti.to/nx-conf/monorepoworld2024), consider [requesting access to the invite-only Enterprise Summit on October 8](https://ti.to/nx-conf/monorepoworld2024), and be sure to stay tuned as we'll be announcing speakers soon!
+
+## Learn more
+
+- [Nx Docs](/getting-started/intro)
+- [X/Twitter](https://twitter.com/nxdevtools) -- [LinkedIn](https://www.linkedin.com/company/nrwl/)
+- [Nx GitHub](https://github.com/nrwl/nx)
+- [Nx Official Discord Server](https://go.nx.dev/community)
+- [Nx Youtube Channel](https://www.youtube.com/@nxdevtools)
+- [Speed up your CI](https://nx.app/)
@@ -46,5 +46,11 @@
    "image": "/blog/images/Zack DeRose.jpeg",
    "twitter": "zackderose",
    "github": "ZackDeRose"
+  },
+  {
+    "name": "Jeff Cross",
+    "image": "/blog/images/Jeff Cross.jpeg",
+    "twitter": "jeffbcross",
+    "github": "jeffbcross"
  }
 ]
@@ -2,10 +2,10 @@

 We were so excited about the features in Nx 18 that we created a whole [Launch Nx Week](/launch-nx) to share our excitement with you. During the launch week, we made the following announcements:

- [Project Crystal](https://blog.nrwl.io/what-if-nx-plugins-were-more-like-vscode-extensions-dcdad140ae09?source=friends_link&sk=ade76fe8d50d44aafb4d4d89ab882e24&__hstc=221401095.5d21139e33f975ecef01c1783a7523db.1673975383152.1708023233215.1708026196201.468&__hssc=221401095.2.1708026196201&__hsfp=589919331) allows you to use inferred tasks
- A new [`@nx/nuxt`](https://blog.nrwl.io/introducing-nx-nuxt-enhanced-nuxt-js-support-in-nx-01eac78034fc?source=friends_link&sk=91582cdbd0719dc23375338ad92afa9b&__hstc=221401095.5d21139e33f975ecef01c1783a7523db.1673975383152.1708023233215.1708026196201.468&__hssc=221401095.2.1708026196201&__hsfp=589919331) plugin is available
- [Nx Agents](https://blog.nrwl.io/fast-effortless-ci-67812514ffb4?source=friends_link&sk=89e1b5c0388dda077e64a2eab5495d95&__hstc=221401095.5d21139e33f975ecef01c1783a7523db.1673975383152.1708023233215.1708026196201.468&__hssc=221401095.2.1708026196201&__hsfp=589919331) are publicly available
- [`nx release`](https://blog.nrwl.io/versioning-and-releasing-packages-in-a-monorepo-45ee194378d1?source=friends_link&sk=934e4c5321774c8a9f88433e0dea578b&__hstc=221401095.5d21139e33f975ecef01c1783a7523db.1673975383152.1708023233215.1708026196201.468&__hssc=221401095.2.1708026196201&__hsfp=589919331) is out of beta
+- [Project Crystal](/blog/what-if-nx-plugins-were-more-like-vscode-extensions) allows you to use inferred tasks
+- A new [`@nx/nuxt`](/blog/introducing-nx-nuxt-enhanced-nuxt-js-support-in-nx) plugin is available
+- [Nx Agents](/blog/fast-effortless-ci) are publicly available
+- [`nx release`](/blog/versioning-and-releasing-packages-in-a-monorepo) is out of beta

 {% youtube
 src="https://youtu.be/Ed1ZCNqWF1Q"
@@ -2,7 +2,7 @@

 Nx 19.0 has landed, and it's ALL about reinforcing 💎Project Crystal💎!!!

-Catch the details in this [blog post](/blog/2024-05-08-nx-19-release) and watch the video below:
+Catch the details in this [blog post](/blog/nx-19-release) and watch the video below:

 {% youtube
 src="https://youtu.be/U6eO8-w9DR0"
@@ -12,16 +12,16 @@ title="Nx 19.0 Has Landed!!"
 ## Features

 {% cards cols="2" %}
-{% card title="NEW PLUGIN: @nx/gradle" type="document" url="/blog/2024-05-08-nx-19-release#new-plugin-nxgradle" /%}
-{% card title="Nx Atomizer Enhancements" type="document" url="/blog/2024-05-08-nx-19-release#nx-atomizer-enhancements" /%}
-{% card title="Associated Technologies Added To Tasks" type="document" url="/blog/2024-05-08-nx-19-release##associated-technologies-added-to-tasks" /%}
-{% card title="Generators to Migrate to Project Crystal" type="document" url="/blog/2024-05-08-nx-19-release#generators-to-migrate-to-project-crystal" /%}
-{% card title="General Crystal Polishing" type="document" url="/blog/2024-05-08-nx-19-release#general-crystal-polishing" /%}
-{% card title="Nx Cloud Updates!" type="document" url="/blog/2024-05-08-nx-19-release#nx-cloud-updates" /%}
-{% card title="More Miscellaneous Updates!" type="document" url="/blog/2024-05-08-nx-19-release#more-miscellaneous-updates" /%}
-{% card title="NEW CONFERENCE: Monorepo World 2024" type="document" url="/blog/2024-05-08-nx-19-release#new-conference-monorepo-world-2024" /%}
+{% card title="NEW PLUGIN: @nx/gradle" type="document" url="/blog/nx-19-release#new-plugin-nxgradle" /%}
+{% card title="Nx Atomizer Enhancements" type="document" url="/blog/nx-19-release#nx-atomizer-enhancements" /%}
+{% card title="Associated Technologies Added To Tasks" type="document" url="/blog/nx-19-release##associated-technologies-added-to-tasks" /%}
+{% card title="Generators to Migrate to Project Crystal" type="document" url="/blog/nx-19-release#generators-to-migrate-to-project-crystal" /%}
+{% card title="General Crystal Polishing" type="document" url="/blog/nx-19-release#general-crystal-polishing" /%}
+{% card title="Nx Cloud Updates!" type="document" url="/blog/nx-19-release#nx-cloud-updates" /%}
+{% card title="More Miscellaneous Updates!" type="document" url="/blog/nx-19-release#more-miscellaneous-updates" /%}
+{% card title="NEW CONFERENCE: Monorepo World 2024" type="document" url="/blog/nx-19-release#new-conference-monorepo-world-2024" /%}
 {% /cards %}

 ## Breaking Changes

-[Updating Bundled Environment Variables: `NX_` to `NX_PUBLIC_`](/blog/2024-05-08-nx-19-release#breaking-change-updating-bundled-environment-variables-to)
+[Updating Bundled Environment Variables: `NX_` to `NX_PUBLIC_`](/blog/nx-19-release#breaking-change-updating-bundled-environment-variables-to)
@@ -0,0 +1,18 @@
+# Nx 19.5 Adds StackBlitz, New Features, And More!!
+
+[![Nx 19.5 Adds StackBlitz, New Features, And More!!](/blog/images/2024-07-25/nx-19-5-thumbnail.png)](/blog/nx-19-5-adds-stackblitz-new-features-and-more)
+
+Read the [blogpost](/blog/nx-19-5-adds-stackblitz-new-features-and-more) for full details.
+
+## Features
+
+{% cards cols="2" %}
+{% card title="Stackblitz Support" type="document" url="/blog/nx-19-5-adds-stackblitz-new-features-and-more#stackblitz-support" /%}
+{% card title="NEW: Pattern Support for `targetDefaults`" type="document" url="/blog/nx-19-5-adds-stackblitz-new-features-and-more#new-pattern-support-for-targetdefaults" /%}
+{% card title="NEW: Individual Targets Can Now Opt Out of Parallelism" type="document" url="/blog/nx-19-5-adds-stackblitz-new-features-and-more#new-individual-targets-can-now-opt-out-of-parallelism" /%}
+{% card title="Experimental: Gradle Test Atomization" type="document" url="/blog/nx-19-5-adds-stackblitz-new-features-and-more#experimental-gradle-test-atomization" /%}
+{% card title="Support for React 19 (rc) and Angular 18.1" type="document" url="/blog/nx-19-5-adds-stackblitz-new-features-and-more#support-for-react-19-rc-and-angular-181" /%}
+{% card title="NEW: Nx Cloud Hobby Tier" type="document" url="/blog/nx-19-5-adds-stackblitz-new-features-and-more#new-nx-cloud-hobby-tier" /%}
+{% card title="Monorepo World Conference Speakers to Be Announced Soon!!" type="document" url="/blog/nx-19-5-adds-stackblitz-new-features-and-more#monorepo-world-conference-speakers-to-be-announced-soon" /%}
+
+{% /cards %}
@@ -59,12 +59,30 @@ Run build for only projects with the tag `dotnet`:
 nx affected -t=build --exclude='*,!tag:dotnet'
 ```

-Use the currently executing project name in your command.:
+Use the currently executing project name in your command:

 ```shell
 nx affected -t build --tag=$NX_TASK_TARGET_PROJECT:latest
 ```

+Preview the task graph that Nx would run inside a webview:
+
+```shell
+ nx affected -t=build --graph
+```
+
+Save the task graph to a file:
+
+```shell
+ nx affected -t=build --graph=output.json
+```
+
+Print the task graph to the console:
+
+```shell
+ nx affected -t=build --graph=stdout
+```
+
 ## Options

 ### ~~all~~
@@ -109,7 +127,7 @@ Change the way Nx is calculating the affected command by providing directly chan

 Type: `string`

-Show the task graph of the command. Pass a file path to save the graph data instead of viewing it in the browser.
+Show the task graph of the command. Pass a file path to save the graph data instead of viewing it in the browser. Pass "stdout" to print the results to the terminal.

 ### head

@@ -147,6 +165,13 @@ Choices: [dynamic, static, stream, stream-without-prefixes]

 Defines how Nx emits outputs tasks logs

+| option                  | description                                                                                                                                                                                                                         |
+| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| dynamic                 | use dynamic output life cycle, previous content is overwritten or modified as new outputs are added, display minimal logs by default, always show errors. This output format is recommended on your local development environments. |
+| static                  | uses static output life cycle, no previous content is rewritten or modified as new outputs are added. This output format is recommened for CI environments.                                                                         |
+| stream                  | nx by default logs output to an internal output stream, enable this option to stream logs to stdout / stderr                                                                                                                        |
+| stream-without-prefixes | nx prefixes the project name the target is running on, use this option remove the project name prefix from output                                                                                                                   |
+
 ### parallel

 Type: `string`
@@ -121,15 +121,15 @@ Generate a 'src/' directory for Next.js

 Type: `string`

-Choices: [yes, github, circleci, skip]
+Choices: [github, circleci, gitlab, azure, bitbucket-pipelines, skip, yes]

-Do you want Nx Cloud to make your CI fast?
+Which CI provider would you like to use?

 ### packageManager

 Type: `string`

-Choices: [npm, pnpm, yarn]
+Choices: [bun, npm, pnpm, yarn]

 Default: `npm`

@@ -183,6 +183,14 @@ Type: `string`

 Stylesheet type to be used with certain stacks

+### useGitHub
+
+Type: `boolean`
+
+Default: `false`
+
+Will you be using GitHub as your git hosting provider?
+
 ### version

 Type: `boolean`
@@ -35,6 +35,12 @@ Generate a static website with project graph into an html file, accompanied by a
 nx graph --file=output.html
 ```

+Print the project graph as JSON to the console:
+
+```shell
+ nx graph --print
+```
+
 Show the graph where every node is either an ancestor or a descendant of todos-feature-main:

 ```shell
@@ -89,7 +95,7 @@ Exclude certain projects from being processed

 Type: `string`

-Output file (e.g. --file=output.json or --file=dep-graph.html)
+Output file (e.g. --file=output.json or --file=dep-graph.html).

 ### files

@@ -141,6 +147,12 @@ Type: `number`

 Bind the project graph server to a specific port.

+### print
+
+Type: `boolean`
+
+Print the project graph to stdout in the terminal.
+
 ### targets

 Type: `string`
@@ -25,12 +25,6 @@ Default: `false`

 Preview the changes without updating files/creating releases

-### first-release
-
-Type: `boolean`
-
-Indicates that this is the first release for the selected release group. If the current version cannot be determined as usual, the version on disk will be used as a fallback. This is useful when using git or the registry to determine the current version of packages, since those sources are only available after the first release. Also indicates that changelog generation should not assume a previous git tag exists and that publishing should not check for the existence of the package before running.
-
 ### groups

 Type: `string`
@@ -73,6 +67,12 @@ nx release [specifier]

 #### Options

+##### first-release
+
+Type: `boolean`
+
+Indicates that this is the first release for the selected release group. If the current version cannot be determined as usual, the version on disk will be used as a fallback. This is useful when using git or the registry to determine the current version of packages, since those sources are only available after the first release. Also indicates that changelog generation should not assume a previous git tag exists and that publishing should not check for the existence of the package before running.
+
 ##### help

 Type: `boolean`
@@ -113,6 +113,12 @@ nx release version [specifier]

 #### Options

+##### first-release
+
+Type: `boolean`
+
+Indicates that this is the first release for the selected release group. If the current version cannot be determined as usual, the version on disk will be used as a fallback. This is useful when using git or the registry to determine the current version of packages, since those sources are only available after the first release. Also indicates that changelog generation should not assume a previous git tag exists and that publishing should not check for the existence of the package before running.
+
 ##### git-commit

 Type: `boolean`
@@ -159,7 +165,7 @@ Show help

 Type: `string`

-The optional prerelease identifier to apply to the version, in the case that the specifier argument has been set to `prerelease`.
+The optional prerelease identifier to apply to the version. This will only be applied in the case that the specifier argument has been set to `prerelease` OR when conventional commits are enabled, in which case it will modify the resolved specifier from conventional commits to be its prerelease equivalent. E.g. minor -> preminor

 ##### specifier

@@ -189,6 +195,12 @@ nx release changelog [version]

 #### Options

+##### first-release
+
+Type: `boolean`
+
+Indicates that this is the first release for the selected release group. If the current version cannot be determined as usual, the version on disk will be used as a fallback. This is useful when using git or the registry to determine the current version of packages, since those sources are only available after the first release. Also indicates that changelog generation should not assume a previous git tag exists and that publishing should not check for the existence of the package before running.
+
 ##### from

 Type: `string`
@@ -297,11 +309,17 @@ Type: `string`

 Exclude certain projects from being processed

+##### first-release
+
+Type: `boolean`
+
+Indicates that this is the first release for the selected release group. If the current version cannot be determined as usual, the version on disk will be used as a fallback. This is useful when using git or the registry to determine the current version of packages, since those sources are only available after the first release. Also indicates that changelog generation should not assume a previous git tag exists and that publishing should not check for the existence of the package before running.
+
 ##### graph

 Type: `string`

-Show the task graph of the command. Pass a file path to save the graph data instead of viewing it in the browser.
+Show the task graph of the command. Pass a file path to save the graph data instead of viewing it in the browser. Pass "stdout" to print the results to the terminal.

 ##### help

@@ -339,6 +357,13 @@ Choices: [dynamic, static, stream, stream-without-prefixes]

 Defines how Nx emits outputs tasks logs

+| option                  | description                                                                                                                                                                                                                         |
+| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| dynamic                 | use dynamic output life cycle, previous content is overwritten or modified as new outputs are added, display minimal logs by default, always show errors. This output format is recommended on your local development environments. |
+| static                  | uses static output life cycle, no previous content is rewritten or modified as new outputs are added. This output format is recommened for CI environments.                                                                         |
+| stream                  | nx by default logs output to an internal output stream, enable this option to stream logs to stdout / stderr                                                                                                                        |
+| stream-without-prefixes | nx prefixes the project name the target is running on, use this option remove the project name prefix from output                                                                                                                   |
+
 ##### parallel

 Type: `string`
@@ -1,11 +1,11 @@
 ---
 title: 'reset - CLI command'
-description: 'Clears all the cached Nx artifacts and metadata about the workspace and shuts down the Nx Daemon.'
+description: 'Clears cached Nx artifacts and metadata about the workspace and shuts down the Nx Daemon.'
 ---

 # reset

-Clears all the cached Nx artifacts and metadata about the workspace and shuts down the Nx Daemon.
+Clears cached Nx artifacts and metadata about the workspace and shuts down the Nx Daemon.

 ## Usage

@@ -14,3 +14,67 @@ nx reset
 ```

 Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpm nx`.
+
+### Examples
+
+Clears the internal state of the daemon and metadata that Nx is tracking. Helpful if you are getting strange errors and want to start fresh:
+
+```shell
+ nx reset
+```
+
+Clears the Nx Cache directory. This will remove all local cache entries for tasks, but will not affect the remote cache:
+
+```shell
+ nx reset --only-cache
+```
+
+Stops the Nx Daemon, it will be restarted fresh when the next Nx command is run.:
+
+```shell
+ nx reset --only-daemon
+```
+
+Clears the workspace data directory. Used by Nx to store cached data about the current workspace (e.g. partial results, incremental data, etc):
+
+```shell
+ nx reset --only-workspace-data
+```
+
+## Options
+
+### help
+
+Type: `boolean`
+
+Show help
+
+### onlyCache
+
+Type: `boolean`
+
+Clears the Nx cache directory. This will remove all local cache entries for tasks, but will not affect the remote cache.
+
+### onlyCloud
+
+Type: `boolean`
+
+Resets the Nx Cloud client. NOTE: Does not clear the remote cache.
+
+### onlyDaemon
+
+Type: `boolean`
+
+Stops the Nx Daemon, it will be restarted fresh when the next Nx command is run.
+
+### onlyWorkspaceData
+
+Type: `boolean`
+
+Clears the workspace data directory. Used by Nx to store cached data about the current workspace (e.g. partial results, incremental data, etc)
+
+### version
+
+Type: `boolean`
+
+Show version number
@@ -71,6 +71,24 @@ Run lint, test, and build targets for all projects. Requires Nx v15.4+:
 nx run-many --targets=lint,test,build
 ```

+Preview the task graph that Nx would run inside a webview:
+
+```shell
+ nx run-many -t=build --graph
+```
+
+Save the task graph to a file:
+
+```shell
+ nx run-many -t=build --graph=output.json
+```
+
+Print the task graph to the console:
+
+```shell
+ nx run-many -t=build --graph=stdout
+```
+
 ## Options

 ### all
@@ -105,7 +123,7 @@ Exclude certain projects from being processed

 Type: `string`

-Show the task graph of the command. Pass a file path to save the graph data instead of viewing it in the browser.
+Show the task graph of the command. Pass a file path to save the graph data instead of viewing it in the browser. Pass "stdout" to print the results to the terminal.

 ### help

@@ -137,6 +155,13 @@ Choices: [dynamic, static, stream, stream-without-prefixes]

 Defines how Nx emits outputs tasks logs

+| option                  | description                                                                                                                                                                                                                         |
+| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| dynamic                 | use dynamic output life cycle, previous content is overwritten or modified as new outputs are added, display minimal logs by default, always show errors. This output format is recommended on your local development environments. |
+| static                  | uses static output life cycle, no previous content is rewritten or modified as new outputs are added. This output format is recommened for CI environments.                                                                         |
+| stream                  | nx by default logs output to an internal output stream, enable this option to stream logs to stdout / stderr                                                                                                                        |
+| stream-without-prefixes | nx prefixes the project name the target is running on, use this option remove the project name prefix from output                                                                                                                   |
+
 ### parallel

 Type: `string`
@@ -1,44 +1,163 @@
 ---
 title: 'run - CLI command'
-description: 'Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.'
+description: 'Run a target for a project
+  (e.g., nx run myapp:serve:production).
+
+  You can also use the infix notation to run a target:
+  (e.g., nx serve myapp --configuration=production)
+
+  You can skip the use of Nx cache by using the --skip-nx-cache option.'
 ---

 # run

-Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.
+Run a target for a project
+(e.g., nx run myapp:serve:production).
+
+    You can also use the infix notation to run a target:
+    (e.g., nx serve myapp --configuration=production)
+
+    You can skip the use of Nx cache by using the --skip-nx-cache option.

 ## Usage

 ```shell
-nx run <target> [options]
+nx run [project][:target][:configuration] [_..]
 ```

-Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpx nx`.
+Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpm nx`.

 ### Examples

-Run the `build` target for the `myapp` :
+Run the target build for the myapp project:

 ```shell
-nx run myapp:build
+ nx run myapp:build
 ```

-Run the `build` target for the `myapp` project with a `production` configuration:
+Run the target build for the myapp project, with production configuration:

 ```shell
-nx run myapp:build:production
+ nx run myapp:build:production
+```
+
+Preview the task graph that Nx would run inside a webview:
+
+```shell
+ nx run myapp:build --graph
+```
+
+Save the task graph to a file:
+
+```shell
+ nx run myapp:build --graph=output.json
+```
+
+Print the task graph to the console:
+
+```shell
+ nx run myapp:build --graph=stdout
+```
+
+Run's a target named build:test for the myapp project. Note the quotes around the target name to prevent "test" from being considered a configuration:
+
+```shell
+ nx run myapp:"build:test"
 ```

 ## Options

-### configuration (-c)
+### batch

-A named builder configuration, defined in the "configurations" section of the workspace configuration file. The builder uses the named configuration to run the given target.
+Type: `boolean`

-### help
+Default: `false`

-Show help
+Run task(s) in batches for executors which support batches
+
+### configuration
+
+Type: `string`
+
+This is the configuration to use when performing tasks on projects
+
+### exclude
+
+Type: `string`
+
+Exclude certain projects from being processed
+
+### graph
+
+Type: `string`
+
+Show the task graph of the command. Pass a file path to save the graph data instead of viewing it in the browser. Pass "stdout" to print the results to the terminal.
+
+### nxBail
+
+Type: `boolean`
+
+Default: `false`
+
+Stop command execution after the first failed task
+
+### nxIgnoreCycles
+
+Type: `boolean`
+
+Default: `false`
+
+Ignore cycles in the task graph
+
+### output-style
+
+Type: `string`
+
+Choices: [dynamic, static, stream, stream-without-prefixes, compact]
+
+Defines how Nx emits outputs tasks logs
+
+| option                  | description                                                                                                                                                                                                                         |
+| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| dynamic                 | use dynamic output life cycle, previous content is overwritten or modified as new outputs are added, display minimal logs by default, always show errors. This output format is recommended on your local development environments. |
+| static                  | uses static output life cycle, no previous content is rewritten or modified as new outputs are added. This output format is recommened for CI environments.                                                                         |
+| stream                  | nx by default logs output to an internal output stream, enable this option to stream logs to stdout / stderr                                                                                                                        |
+| stream-without-prefixes | nx prefixes the project name the target is running on, use this option remove the project name prefix from output                                                                                                                   |
+
+### parallel
+
+Type: `string`
+
+Max number of parallel processes [default is 3]
+
+### project
+
+Type: `string`
+
+Target project
+
+### runner
+
+Type: `string`
+
+This is the name of the tasks runner configured in nx.json
+
+### skipNxCache
+
+Type: `boolean`
+
+Default: `false`
+
+Rerun the tasks even when the results are available in the cache
+
+### verbose
+
+Type: `boolean`
+
+Prints additional information about the commands (e.g., stack traces)

 ### version

+Type: `boolean`
+
 Show version number
@@ -23,12 +23,18 @@ Show all projects in the workspace:
 nx show projects
 ```

-Show all projects with names starting with "api-". The "projects" option is useful to see which projects would be selected by run-many.:
+Show all projects with names starting with "api-". The "projects" option is useful to see which projects would be selected by run-many:

 ```shell
 nx show projects --projects api-*
 ```

+Show all projects with a tag starting with "ui-". The "projects" option is useful to see which projects would be selected by run-many:
+
+```shell
+ nx show projects --projects tag:ui-*
+```
+
 Show all projects with a serve target:

 ```shell
@@ -53,13 +59,19 @@ Show affected projects in the workspace, excluding end-to-end projects:
 nx show projects --affected --exclude=*-e2e
 ```

-Show detailed information about "my-app" in a json format.:
+If in an interactive terminal, opens the project detail view. If not in an interactive terminal, defaults to JSON:

 ```shell
 nx show project my-app
 ```

-Show information about "my-app" in a human readable format.:
+Show detailed information about "my-app" in a json format:
+
+```shell
+ nx show project my-app --json
+```
+
+Show information about "my-app" in a human readable format:

 ```shell
 nx show project my-app --json false
@@ -233,4 +245,4 @@ Show version number

 Type: `boolean`

-Show project details in the browser
+Show project details in the browser. (default when interactive)
@@ -0,0 +1,197 @@
+# Class: AggregateCreateNodesError
+
+This error should be thrown when a `createNodesV2` function hits a recoverable error.
+It allows Nx to recieve partial results and continue processing for better UX.
+
+## Hierarchy
+
+- `Error`
+
+  ↳ **`AggregateCreateNodesError`**
+
+## Table of contents
+
+### Constructors
+
+- [constructor](../../devkit/documents/AggregateCreateNodesError#constructor)
+
+### Properties
+
+- [cause](../../devkit/documents/AggregateCreateNodesError#cause): unknown
+- [errors](../../devkit/documents/AggregateCreateNodesError#errors): [file: string, error: Error][]
+- [message](../../devkit/documents/AggregateCreateNodesError#message): string
+- [name](../../devkit/documents/AggregateCreateNodesError#name): string
+- [partialResults](../../devkit/documents/AggregateCreateNodesError#partialresults): CreateNodesResultV2
+- [stack](../../devkit/documents/AggregateCreateNodesError#stack): string
+- [prepareStackTrace](../../devkit/documents/AggregateCreateNodesError#preparestacktrace): Function
+- [stackTraceLimit](../../devkit/documents/AggregateCreateNodesError#stacktracelimit): number
+
+### Methods
+
+- [captureStackTrace](../../devkit/documents/AggregateCreateNodesError#capturestacktrace)
+
+## Constructors
+
+### constructor
+
+• **new AggregateCreateNodesError**(`errors`, `partialResults`): [`AggregateCreateNodesError`](../../devkit/documents/AggregateCreateNodesError)
+
+Throwing this error from a `createNodesV2` function will allow Nx to continue processing and recieve partial results from your plugin.
+
+#### Parameters
+
+| Name             | Type                                                                | Description                                                                                                                                                                                                      |
+| :--------------- | :------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `errors`         | [file: string, error: Error][]                                      | An array of tuples that represent errors encountered when processing a given file. An example entry might look like ['path/to/project.json', [Error: 'Invalid JSON. Unexpected token 'a' in JSON at position 0]] |
+| `partialResults` | [`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2) | The partial results of the `createNodesV2` function. This should be the results for each file that didn't encounter an issue.                                                                                    |
+
+#### Returns
+
+[`AggregateCreateNodesError`](../../devkit/documents/AggregateCreateNodesError)
+
+**`Example`**
+
+```ts
+export async function createNodesV2(files: string[]) {
+  const partialResults = [];
+  const errors = [];
+  await Promise.all(
+    files.map(async (file) => {
+      try {
+        const result = await createNodes(file);
+        partialResults.push(result);
+      } catch (e) {
+        errors.push([file, e]);
+      }
+    })
+  );
+  if (errors.length > 0) {
+    throw new AggregateCreateNodesError(errors, partialResults);
+  }
+  return partialResults;
+}
+```
+
+#### Overrides
+
+Error.constructor
+
+## Properties
+
+### cause
+
+• `Optional` **cause**: `unknown`
+
+#### Inherited from
+
+Error.cause
+
+---
+
+### errors
+
+• `Readonly` **errors**: [file: string, error: Error][]
+
+An array of tuples that represent errors encountered when processing a given file. An example entry might look like ['path/to/project.json', [Error: 'Invalid JSON. Unexpected token 'a' in JSON at position 0]]
+
+---
+
+### message
+
+• **message**: `string`
+
+#### Inherited from
+
+Error.message
+
+---
+
+### name
+
+• **name**: `string`
+
+#### Inherited from
+
+Error.name
+
+---
+
+### partialResults
+
+• `Readonly` **partialResults**: [`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2)
+
+The partial results of the `createNodesV2` function. This should be the results for each file that didn't encounter an issue.
+
+---
+
+### stack
+
+• `Optional` **stack**: `string`
+
+#### Inherited from
+
+Error.stack
+
+---
+
+### prepareStackTrace
+
+▪ `Static` `Optional` **prepareStackTrace**: (`err`: `Error`, `stackTraces`: `CallSite`[]) => `any`
+
+Optional override for formatting stack traces
+
+**`See`**
+
+https://v8.dev/docs/stack-trace-api#customizing-stack-traces
+
+#### Type declaration
+
+▸ (`err`, `stackTraces`): `any`
+
+##### Parameters
+
+| Name          | Type         |
+| :------------ | :----------- |
+| `err`         | `Error`      |
+| `stackTraces` | `CallSite`[] |
+
+##### Returns
+
+`any`
+
+#### Inherited from
+
+Error.prepareStackTrace
+
+---
+
+### stackTraceLimit
+
+▪ `Static` **stackTraceLimit**: `number`
+
+#### Inherited from
+
+Error.stackTraceLimit
+
+## Methods
+
+### captureStackTrace
+
+▸ **captureStackTrace**(`targetObject`, `constructorOpt?`): `void`
+
+Create .stack property on a target object
+
+#### Parameters
+
+| Name              | Type       |
+| :---------------- | :--------- |
+| `targetObject`    | `object`   |
+| `constructorOpt?` | `Function` |
+
+#### Returns
+
+`void`
+
+#### Inherited from
+
+Error.captureStackTrace
@@ -0,0 +1,26 @@
+# Type alias: AsyncIteratorExecutor\<T\>
+
+Ƭ **AsyncIteratorExecutor**\<`T`\>: (`options`: `T`, `context`: [`ExecutorContext`](../../devkit/documents/ExecutorContext)) => `AsyncIterableIterator`\<\{ `success`: `boolean` }\>
+
+An executor implementation that returns an async iterator
+
+#### Type parameters
+
+| Name | Type  |
+| :--- | :---- |
+| `T`  | `any` |
+
+#### Type declaration
+
+▸ (`options`, `context`): `AsyncIterableIterator`\<\{ `success`: `boolean` }\>
+
+##### Parameters
+
+| Name      | Type                                                        |
+| :-------- | :---------------------------------------------------------- |
+| `options` | `T`                                                         |
+| `context` | [`ExecutorContext`](../../devkit/documents/ExecutorContext) |
+
+##### Returns
+
+`AsyncIterableIterator`\<\{ `success`: `boolean` }\>
@@ -4,6 +4,18 @@

 A pair of file patterns and [CreateNodesFunction](../../devkit/documents/CreateNodesFunction)

+Nx 19.2+: Both original `CreateNodes` and `CreateNodesV2` are supported. Nx will only invoke `CreateNodesV2` if it is present.
+Nx 20.X : The `CreateNodesV2` will be the only supported API. This typing will still exist, but be identical to `CreateNodesV2`.
+Nx **will not** invoke the original `plugin.createNodes` callback. This should give plugin authors a window to transition.
+Plugin authors should update their plugin's `createNodes` function to align with `CreateNodesV2` / the updated `CreateNodes`.
+The plugin should contain something like: `export createNodes = createNodesV2;` during this period. This will allow the plugin
+to maintain compatibility with Nx 19.2 and up.
+Nx 21.X : The `CreateNodesV2` typing will be removed, as it has replaced `CreateNodes`.
+
+**`Deprecated`**
+
+Use [CreateNodesV2](../../devkit/documents/CreateNodesV2) instead. CreateNodesV2 will replace this API. Read more about the transition above.
+
 #### Type parameters

 | Name | Type      |
@@ -2,6 +2,12 @@

 Context for [CreateNodesFunction](../../devkit/documents/CreateNodesFunction)

+## Hierarchy
+
+- [`CreateNodesContextV2`](../../devkit/documents/CreateNodesContextV2)
+
+  ↳ **`CreateNodesContext`**
+
 ## Table of contents

 ### Properties
@@ -24,8 +30,16 @@ The subset of configuration files which match the createNodes pattern

 • `Readonly` **nxJsonConfiguration**: [`NxJsonConfiguration`](../../devkit/documents/NxJsonConfiguration)\<`string`[] \| `"*"`\>

+#### Inherited from
+
+[CreateNodesContextV2](../../devkit/documents/CreateNodesContextV2).[nxJsonConfiguration](../../devkit/documents/CreateNodesContextV2#nxjsonconfiguration)
+
 ---

 ### workspaceRoot

 • `Readonly` **workspaceRoot**: `string`
+
+#### Inherited from
+
+[CreateNodesContextV2](../../devkit/documents/CreateNodesContextV2).[workspaceRoot](../../devkit/documents/CreateNodesContextV2#workspaceroot)
@@ -0,0 +1,26 @@
+# Interface: CreateNodesContextV2
+
+## Hierarchy
+
+- **`CreateNodesContextV2`**
+
+  ↳ [`CreateNodesContext`](../../devkit/documents/CreateNodesContext)
+
+## Table of contents
+
+### Properties
+
+- [nxJsonConfiguration](../../devkit/documents/CreateNodesContextV2#nxjsonconfiguration): NxJsonConfiguration<string[] | "\*">
+- [workspaceRoot](../../devkit/documents/CreateNodesContextV2#workspaceroot): string
+
+## Properties
+
+### nxJsonConfiguration
+
+• `Readonly` **nxJsonConfiguration**: [`NxJsonConfiguration`](../../devkit/documents/NxJsonConfiguration)\<`string`[] \| `"*"`\>
+
+---
+
+### workspaceRoot
+
+• `Readonly` **workspaceRoot**: `string`
@@ -0,0 +1,25 @@
+# Type alias: CreateNodesFunctionV2\<T\>
+
+Ƭ **CreateNodesFunctionV2**\<`T`\>: (`projectConfigurationFiles`: readonly `string`[], `options`: `T` \| `undefined`, `context`: [`CreateNodesContextV2`](../../devkit/documents/CreateNodesContextV2)) => [`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2) \| `Promise`\<[`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2)\>
+
+#### Type parameters
+
+| Name | Type      |
+| :--- | :-------- |
+| `T`  | `unknown` |
+
+#### Type declaration
+
+▸ (`projectConfigurationFiles`, `options`, `context`): [`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2) \| `Promise`\<[`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2)\>
+
+##### Parameters
+
+| Name                        | Type                                                                  |
+| :-------------------------- | :-------------------------------------------------------------------- |
+| `projectConfigurationFiles` | readonly `string`[]                                                   |
+| `options`                   | `T` \| `undefined`                                                    |
+| `context`                   | [`CreateNodesContextV2`](../../devkit/documents/CreateNodesContextV2) |
+
+##### Returns
+
+[`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2) \| `Promise`\<[`CreateNodesResultV2`](../../devkit/documents/CreateNodesResultV2)\>
@@ -0,0 +1,3 @@
+# Type alias: CreateNodesResultV2
+
+Ƭ **CreateNodesResultV2**: readonly [configFileSource: string, result: CreateNodesResult][]
@@ -0,0 +1,12 @@
+# Type alias: CreateNodesV2\<T\>
+
+Ƭ **CreateNodesV2**\<`T`\>: readonly [projectFilePattern: string, createNodesFunction: CreateNodesFunctionV2\<T\>]
+
+A pair of file patterns and [CreateNodesFunctionV2](../../devkit/documents/CreateNodesFunctionV2)
+In Nx 20 [CreateNodes](../../devkit/documents/CreateNodes) will be replaced with this type. In Nx 21, this type will be removed.
+
+#### Type parameters
+
+| Name | Type      |
+| :--- | :-------- |
+| `T`  | `unknown` |
@@ -1,6 +1,6 @@
 # Type alias: Executor\<T\>

-Ƭ **Executor**\<`T`\>: (`options`: `T`, `context`: [`ExecutorContext`](../../devkit/documents/ExecutorContext)) => `Promise`\<\{ `success`: `boolean` }\> \| `AsyncIterableIterator`\<\{ `success`: `boolean` }\>
+Ƭ **Executor**\<`T`\>: [`PromiseExecutor`](../../devkit/documents/PromiseExecutor)\<`T`\> \| [`AsyncIteratorExecutor`](../../devkit/documents/AsyncIteratorExecutor)\<`T`\>

 Implementation of a target of a project

@@ -9,18 +9,3 @@ Implementation of a target of a project
 | Name | Type  |
 | :--- | :---- |
 | `T`  | `any` |
-
-#### Type declaration
-
-▸ (`options`, `context`): `Promise`\<\{ `success`: `boolean` }\> \| `AsyncIterableIterator`\<\{ `success`: `boolean` }\>
-
-##### Parameters
-
-| Name      | Type                                                        |
-| :-------- | :---------------------------------------------------------- |
-| `options` | `T`                                                         |
-| `context` | [`ExecutorContext`](../../devkit/documents/ExecutorContext) |
-
-##### Returns
-
-`Promise`\<\{ `success`: `boolean` }\> \| `AsyncIterableIterator`\<\{ `success`: `boolean` }\>
@@ -12,9 +12,10 @@ A plugin for Nx which creates nodes and dependencies for the [ProjectGraph](../.

 #### Type declaration

-| Name                  | Type                                                                            | Description                                                                                                                                   |
-| :-------------------- | :------------------------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------- |
-| `createDependencies?` | [`CreateDependencies`](../../devkit/documents/CreateDependencies)\<`TOptions`\> | Provides a function to analyze files to create dependencies for the [ProjectGraph](../../devkit/documents/ProjectGraph)                       |
-| `createMetadata?`     | [`CreateMetadata`](../../devkit/documents/CreateMetadata)\<`TOptions`\>         | Provides a function to create metadata for the [ProjectGraph](../../devkit/documents/ProjectGraph)                                            |
-| `createNodes?`        | [`CreateNodes`](../../devkit/documents/CreateNodes)\<`TOptions`\>               | Provides a file pattern and function that retrieves configuration info from those files. e.g. { '\*_/_.csproj': buildProjectsFromCsProjFile } |
-| `name`                | `string`                                                                        | -                                                                                                                                             |
+| Name                  | Type                                                                            | Description                                                                                                                                                                                                                                                                                     |
+| :-------------------- | :------------------------------------------------------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `createDependencies?` | [`CreateDependencies`](../../devkit/documents/CreateDependencies)\<`TOptions`\> | Provides a function to analyze files to create dependencies for the [ProjectGraph](../../devkit/documents/ProjectGraph)                                                                                                                                                                         |
+| `createMetadata?`     | [`CreateMetadata`](../../devkit/documents/CreateMetadata)\<`TOptions`\>         | Provides a function to create metadata for the [ProjectGraph](../../devkit/documents/ProjectGraph)                                                                                                                                                                                              |
+| `createNodes?`        | [`CreateNodes`](../../devkit/documents/CreateNodes)\<`TOptions`\>               | Provides a file pattern and function that retrieves configuration info from those files. e.g. { '**/\*.csproj': buildProjectsFromCsProjFile } **`Deprecated`\*\* Use createNodesV2 instead. In Nx 20 support for calling createNodes with a single file for the first argument will be removed. |
+| `createNodesV2?`      | [`CreateNodesV2`](../../devkit/documents/CreateNodesV2)\<`TOptions`\>           | Provides a file pattern and function that retrieves configuration info from those files. e.g. { '\*_/_.csproj': buildProjectsFromCsProjFiles } In Nx 20 createNodes will be replaced with this property. In Nx 21, this property will be removed.                                               |
+| `name`                | `string`                                                                        | -                                                                                                                                                                                                                                                                                               |
@@ -0,0 +1,29 @@
+# Enumeration: OverwriteStrategy
+
+Specify what should be done when a file is generated but already exists on the system
+
+## Table of contents
+
+### Enumeration Members
+
+- [KeepExisting](../../devkit/documents/OverwriteStrategy#keepexisting)
+- [Overwrite](../../devkit/documents/OverwriteStrategy#overwrite)
+- [ThrowIfExisting](../../devkit/documents/OverwriteStrategy#throwifexisting)
+
+## Enumeration Members
+
+### KeepExisting
+
+• **KeepExisting** = `"keepExisting"`
+
+---
+
+### Overwrite
+
+• **Overwrite** = `"overwrite"`
+
+---
+
+### ThrowIfExisting
+
+• **ThrowIfExisting** = `"throwIfExisting"`
@@ -1,3 +1,3 @@
 # Type alias: PackageManager

-Ƭ **PackageManager**: `"yarn"` \| `"pnpm"` \| `"npm"`
+Ƭ **PackageManager**: `"yarn"` \| `"pnpm"` \| `"npm"` \| `"bun"`
@@ -0,0 +1,26 @@
+# Type alias: PromiseExecutor\<T\>
+
+Ƭ **PromiseExecutor**\<`T`\>: (`options`: `T`, `context`: [`ExecutorContext`](../../devkit/documents/ExecutorContext)) => `Promise`\<\{ `success`: `boolean` }\>
+
+An executor implementation that returns a promise
+
+#### Type parameters
+
+| Name | Type  |
+| :--- | :---- |
+| `T`  | `any` |
+
+#### Type declaration
+
+▸ (`options`, `context`): `Promise`\<\{ `success`: `boolean` }\>
+
+##### Parameters
+
+| Name      | Type                                                        |
+| :-------- | :---------------------------------------------------------- |
+| `options` | `T`                                                         |
+| `context` | [`ExecutorContext`](../../devkit/documents/ExecutorContext) |
+
+##### Returns
+
+`Promise`\<\{ `success`: `boolean` }\>
@@ -15,15 +15,18 @@ It only uses language primitives and immutable objects

 - [ChangeType](../../devkit/documents/ChangeType)
 - [DependencyType](../../devkit/documents/DependencyType)
+- [OverwriteStrategy](../../devkit/documents/OverwriteStrategy)

 ### Classes

+- [AggregateCreateNodesError](../../devkit/documents/AggregateCreateNodesError)
 - [ProjectGraphBuilder](../../devkit/documents/ProjectGraphBuilder)

 ### Interfaces

 - [CreateDependenciesContext](../../devkit/documents/CreateDependenciesContext)
 - [CreateNodesContext](../../devkit/documents/CreateNodesContext)
+- [CreateNodesContextV2](../../devkit/documents/CreateNodesContextV2)
 - [CreateNodesResult](../../devkit/documents/CreateNodesResult)
 - [DefaultTasksRunnerOptions](../../devkit/documents/DefaultTasksRunnerOptions)
 - [ExecutorContext](../../devkit/documents/ExecutorContext)
@@ -62,11 +65,15 @@ It only uses language primitives and immutable objects

 ### Type Aliases

+- [AsyncIteratorExecutor](../../devkit/documents/AsyncIteratorExecutor)
 - [CreateDependencies](../../devkit/documents/CreateDependencies)
 - [CreateMetadata](../../devkit/documents/CreateMetadata)
 - [CreateMetadataContext](../../devkit/documents/CreateMetadataContext)
 - [CreateNodes](../../devkit/documents/CreateNodes)
 - [CreateNodesFunction](../../devkit/documents/CreateNodesFunction)
+- [CreateNodesFunctionV2](../../devkit/documents/CreateNodesFunctionV2)
+- [CreateNodesResultV2](../../devkit/documents/CreateNodesResultV2)
+- [CreateNodesV2](../../devkit/documents/CreateNodesV2)
 - [CustomHasher](../../devkit/documents/CustomHasher)
 - [DynamicDependency](../../devkit/documents/DynamicDependency)
 - [Executor](../../devkit/documents/Executor)
@@ -85,6 +92,7 @@ It only uses language primitives and immutable objects
 - [ProjectTargetConfigurator](../../devkit/documents/ProjectTargetConfigurator)
 - [ProjectType](../../devkit/documents/ProjectType)
 - [ProjectsMetadata](../../devkit/documents/ProjectsMetadata)
+- [PromiseExecutor](../../devkit/documents/PromiseExecutor)
 - [RawProjectGraphDependency](../../devkit/documents/RawProjectGraphDependency)
 - [StaticDependency](../../devkit/documents/StaticDependency)
 - [StringChange](../../devkit/documents/StringChange)
@@ -109,6 +117,7 @@ It only uses language primitives and immutable objects
 - [applyChangesToString](../../devkit/documents/applyChangesToString)
 - [convertNxExecutor](../../devkit/documents/convertNxExecutor)
 - [convertNxGenerator](../../devkit/documents/convertNxGenerator)
+- [createNodesFromFiles](../../devkit/documents/createNodesFromFiles)
 - [createProjectFileMapUsingProjectGraph](../../devkit/documents/createProjectFileMapUsingProjectGraph)
 - [createProjectGraphAsync](../../devkit/documents/createProjectGraphAsync)
 - [defaultTasksRunner](../../devkit/documents/defaultTasksRunner)
@@ -123,8 +132,10 @@ It only uses language primitives and immutable objects
 - [getProjects](../../devkit/documents/getProjects)
 - [getWorkspaceLayout](../../devkit/documents/getWorkspaceLayout)
 - [glob](../../devkit/documents/glob)
+- [globAsync](../../devkit/documents/globAsync)
 - [hashArray](../../devkit/documents/hashArray)
 - [installPackagesTask](../../devkit/documents/installPackagesTask)
+- [isDaemonEnabled](../../devkit/documents/isDaemonEnabled)
 - [isWorkspacesEnabled](../../devkit/documents/isWorkspacesEnabled)
 - [joinPathFragments](../../devkit/documents/joinPathFragments)
 - [moveFilesToNewDirectory](../../devkit/documents/moveFilesToNewDirectory)
@@ -22,6 +22,7 @@ Target's configuration
 - [metadata](../../devkit/documents/TargetConfiguration#metadata): TargetMetadata
 - [options](../../devkit/documents/TargetConfiguration#options): T
 - [outputs](../../devkit/documents/TargetConfiguration#outputs): string[]
+- [parallelism](../../devkit/documents/TargetConfiguration#parallelism): boolean

 ## Properties

@@ -109,3 +110,12 @@ Target's options. They are passed in to the executor.

 List of the target's outputs. The outputs will be cached by the Nx computation
 caching engine.
+
+---
+
+### parallelism
+
+• `Optional` **parallelism**: `boolean`
+
+Whether this target can be run in parallel with other tasks
+Default is true
@@ -13,6 +13,7 @@ A representation of the invocation of an Executor
 - [id](../../devkit/documents/Task#id): string
 - [outputs](../../devkit/documents/Task#outputs): string[]
 - [overrides](../../devkit/documents/Task#overrides): any
+- [parallelism](../../devkit/documents/Task#parallelism): boolean
 - [projectRoot](../../devkit/documents/Task#projectroot): string
 - [startTime](../../devkit/documents/Task#starttime): number
 - [target](../../devkit/documents/Task#target): Object
@@ -84,6 +85,14 @@ Overrides for the configured options of the target

 ---

+### parallelism
+
+• **parallelism**: `boolean`
+
+Determines if a given task should be parallelizable.
+
+---
+
 ### projectRoot

 • `Optional` **projectRoot**: `string`
@@ -4,8 +4,9 @@

 #### Type declaration

-| Name        | Type                            |
-| :---------- | :------------------------------ |
-| `extension` | `".js"` \| `".mjs"` \| `".cjs"` |
-| `module?`   | `ModuleKind`                    |
-| `target?`   | `ScriptTarget`                  |
+| Name         | Type                            |
+| :----------- | :------------------------------ |
+| `extension?` | `".js"` \| `".mjs"` \| `".cjs"` |
+| `module?`    | `ModuleKind`                    |
+| `target?`    | `ScriptTarget`                  |
+| `useJsx?`    | `boolean`                       |
@@ -0,0 +1,22 @@
+# Function: createNodesFromFiles
+
+▸ **createNodesFromFiles**\<`T`\>(`createNodes`, `configFiles`, `options`, `context`): `Promise`\<[file: string, value: CreateNodesResult][]\>
+
+#### Type parameters
+
+| Name | Type      |
+| :--- | :-------- |
+| `T`  | `unknown` |
+
+#### Parameters
+
+| Name          | Type                                                                       |
+| :------------ | :------------------------------------------------------------------------- |
+| `createNodes` | [`CreateNodesFunction`](../../devkit/documents/CreateNodesFunction)\<`T`\> |
+| `configFiles` | readonly `string`[]                                                        |
+| `options`     | `T`                                                                        |
+| `context`     | [`CreateNodesContextV2`](../../devkit/documents/CreateNodesContextV2)      |
+
+#### Returns
+
+`Promise`\<[file: string, value: CreateNodesResult][]\>
@@ -1,6 +1,6 @@
 # Function: generateFiles

-▸ **generateFiles**(`tree`, `srcFolder`, `target`, `substitutions`): `void`
+▸ **generateFiles**(`tree`, `srcFolder`, `target`, `substitutions`, `options?`): `void`

 Generates a folder of files based on provided templates.

@@ -32,6 +32,7 @@ doesn't get confused about incorrect TypeScript files.
 | `srcFolder`     | `string`                              | the source folder of files (absolute path)    |
 | `target`        | `string`                              | the target folder (relative to the tree root) |
 | `substitutions` | `Object`                              | an object of key-value pairs                  |
+| `options?`      | `GenerateFilesOptions`                | See GenerateFilesOptions                      |

 #### Returns

@@ -18,3 +18,7 @@ Paths should be unix-style with forward slashes.
 `string`[]

 Normalized paths in the workspace that match the provided glob patterns.
+
+**`Deprecated`**
+
+Use [globAsync](../../devkit/documents/globAsync) instead.
@@ -0,0 +1,20 @@
+# Function: globAsync
+
+▸ **globAsync**(`tree`, `patterns`): `Promise`\<`string`[]\>
+
+Performs a tree-aware glob search on the files in a workspace. Able to find newly
+created files and hides deleted files before the updates are committed to disk.
+Paths should be unix-style with forward slashes.
+
+#### Parameters
+
+| Name       | Type                                  | Description             |
+| :--------- | :------------------------------------ | :---------------------- |
+| `tree`     | [`Tree`](../../devkit/documents/Tree) | The file system tree    |
+| `patterns` | `string`[]                            | A list of glob patterns |
+
+#### Returns
+
+`Promise`\<`string`[]\>
+
+Normalized paths in the workspace that match the provided glob patterns.
@@ -0,0 +1,7 @@
+# Function: isDaemonEnabled
+
+▸ **isDaemonEnabled**(): `boolean`
+
+#### Returns
+
+`boolean`
@@ -28,6 +28,17 @@
        "path": "/ci/intro/why-nx-cloud",
        "tags": []
      },
+      {
+        "id": "connect-to-nx-cloud",
+        "name": "Connect to Nx Cloud",
+        "description": "",
+        "mediaImage": "",
+        "file": "nx-cloud/intro/connect-to-cloud",
+        "itemList": [],
+        "isExternal": false,
+        "path": "/ci/intro/connect-to-nx-cloud",
+        "tags": []
+      },
      {
        "id": "tutorials",
        "name": "Tutorials",
@@ -89,6 +100,17 @@
    "path": "/ci/intro/why-nx-cloud",
    "tags": []
  },
+  "/ci/intro/connect-to-nx-cloud": {
+    "id": "connect-to-nx-cloud",
+    "name": "Connect to Nx Cloud",
+    "description": "",
+    "mediaImage": "",
+    "file": "nx-cloud/intro/connect-to-cloud",
+    "itemList": [],
+    "isExternal": false,
+    "path": "/ci/intro/connect-to-nx-cloud",
+    "tags": []
+  },
  "/ci/intro/tutorials": {
    "id": "tutorials",
    "name": "Tutorials",
@@ -185,6 +207,17 @@
        "path": "/ci/features/distribute-task-execution",
        "tags": []
      },
+      {
+        "id": "nx-cloud-ai",
+        "name": "Nx Cloud AI",
+        "description": "Learn how to enable AI features in Nx Cloud, and what features it enables",
+        "mediaImage": "",
+        "file": "nx-cloud/features/ai-features",
+        "itemList": [],
+        "isExternal": false,
+        "path": "/ci/features/nx-cloud-ai",
+        "tags": []
+      },
      {
        "id": "dynamic-agents",
        "name": "Dynamically Allocate Agents",
@@ -217,17 +250,6 @@
        "isExternal": false,
        "path": "/ci/features/flaky-tasks",
        "tags": []
-      },
-      {
-        "id": "on-premise",
-        "name": "Set up Nx Cloud On-Premise",
-        "description": "Set up Nx Cloud on machines that you control",
-        "mediaImage": "",
-        "file": "nx-cloud/features/nx-enterprise-on-prem",
-        "itemList": [],
-        "isExternal": false,
-        "path": "/ci/features/on-premise",
-        "tags": ["on-premise"]
      }
    ],
    "isExternal": false,
@@ -267,6 +289,17 @@
    "path": "/ci/features/distribute-task-execution",
    "tags": []
  },
+  "/ci/features/nx-cloud-ai": {
+    "id": "nx-cloud-ai",
+    "name": "Nx Cloud AI",
+    "description": "Learn how to enable AI features in Nx Cloud, and what features it enables",
+    "mediaImage": "",
+    "file": "nx-cloud/features/ai-features",
+    "itemList": [],
+    "isExternal": false,
+    "path": "/ci/features/nx-cloud-ai",
+    "tags": []
+  },
  "/ci/features/dynamic-agents": {
    "id": "dynamic-agents",
    "name": "Dynamically Allocate Agents",
@@ -300,17 +333,6 @@
    "path": "/ci/features/flaky-tasks",
    "tags": []
  },
-  "/ci/features/on-premise": {
-    "id": "on-premise",
-    "name": "Set up Nx Cloud On-Premise",
-    "description": "Set up Nx Cloud on machines that you control",
-    "mediaImage": "",
-    "file": "nx-cloud/features/nx-enterprise-on-prem",
-    "itemList": [],
-    "isExternal": false,
-    "path": "/ci/features/on-premise",
-    "tags": ["on-premise"]
-  },
  "/ci/concepts": {
    "id": "concepts",
    "name": "Concepts",
@@ -425,17 +447,6 @@
        "mediaImage": "",
        "file": "",
        "itemList": [
-          {
-            "id": "connect-to-cloud",
-            "name": "Connect Nx Cloud",
-            "description": "",
-            "mediaImage": "",
-            "file": "nx-cloud/recipes/connect-to-cloud",
-            "itemList": [],
-            "isExternal": false,
-            "path": "/ci/recipes/set-up/connect-to-cloud",
-            "tags": []
-          },
          {
            "id": "monorepo-ci-azure",
            "name": "Setting up Azure Pipelines",
@@ -571,14 +582,14 @@
            "tags": []
          },
          {
-            "id": "bitbucket-cloud",
-            "name": "Enable Bitbucket Cloud PR Integration",
+            "id": "bitbucket",
+            "name": "Enable Bitbucket PR Integration",
            "description": "",
            "mediaImage": "",
-            "file": "nx-cloud/set-up/bitbucket-cloud",
+            "file": "nx-cloud/set-up/bitbucket",
            "itemList": [],
            "isExternal": false,
-            "path": "/ci/recipes/source-control-integration/bitbucket-cloud",
+            "path": "/ci/recipes/source-control-integration/bitbucket",
            "tags": []
          },
          {
@@ -622,6 +633,17 @@
            "mediaImage": "",
            "file": "",
            "itemList": [
+              {
+                "id": "on-premise",
+                "name": "Set up Nx Cloud On-Premise",
+                "description": "Set up Nx Cloud on machines that you control",
+                "mediaImage": "",
+                "file": "nx-cloud/features/nx-enterprise-on-prem",
+                "itemList": [],
+                "isExternal": false,
+                "path": "/ci/recipes/enterprise/on-premise/on-premise",
+                "tags": ["on-premise"]
+              },
              {
                "id": "auth-single-admin",
                "name": "Authenticate with a Single Admin",
@@ -677,6 +699,17 @@
                "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket",
                "tags": []
              },
+              {
+                "id": "auth-bitbucket-data-center",
+                "name": "Authenticate with BitBucket Data Center",
+                "description": "",
+                "mediaImage": "",
+                "file": "nx-cloud/enterprise/on-premise/auth-bitbucket-data-center",
+                "itemList": [],
+                "isExternal": false,
+                "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket-data-center",
+                "tags": []
+              },
              {
                "id": "auth-saml",
                "name": "Authenticate via SAML",
@@ -688,17 +721,6 @@
                "path": "/ci/recipes/enterprise/on-premise/auth-saml",
                "tags": []
              },
-              {
-                "id": "auth-saml-managed",
-                "name": "Authenticate via SAML on Managed Version",
-                "description": "",
-                "mediaImage": "",
-                "file": "nx-cloud/enterprise/on-premise/auth-saml-managed",
-                "itemList": [],
-                "isExternal": false,
-                "path": "/ci/recipes/enterprise/on-premise/auth-saml-managed",
-                "tags": []
-              },
              {
                "id": "advanced-config",
                "name": "Advanced Configuration",
@@ -709,6 +731,17 @@
                "isExternal": false,
                "path": "/ci/recipes/enterprise/on-premise/advanced-config",
                "tags": []
+              },
+              {
+                "id": "custom-github-app",
+                "name": "Custom GitHub App",
+                "description": "",
+                "mediaImage": "",
+                "file": "nx-cloud/enterprise/on-premise/custom-github-app",
+                "itemList": [],
+                "isExternal": false,
+                "path": "/ci/recipes/enterprise/on-premise/custom-github-app",
+                "tags": []
              }
            ],
            "isExternal": false,
@@ -844,17 +877,6 @@
    "mediaImage": "",
    "file": "",
    "itemList": [
-      {
-        "id": "connect-to-cloud",
-        "name": "Connect Nx Cloud",
-        "description": "",
-        "mediaImage": "",
-        "file": "nx-cloud/recipes/connect-to-cloud",
-        "itemList": [],
-        "isExternal": false,
-        "path": "/ci/recipes/set-up/connect-to-cloud",
-        "tags": []
-      },
      {
        "id": "monorepo-ci-azure",
        "name": "Setting up Azure Pipelines",
@@ -926,17 +948,6 @@
    "path": "/ci/recipes/set-up",
    "tags": ["distribute-task-execution"]
  },
-  "/ci/recipes/set-up/connect-to-cloud": {
-    "id": "connect-to-cloud",
-    "name": "Connect Nx Cloud",
-    "description": "",
-    "mediaImage": "",
-    "file": "nx-cloud/recipes/connect-to-cloud",
-    "itemList": [],
-    "isExternal": false,
-    "path": "/ci/recipes/set-up/connect-to-cloud",
-    "tags": []
-  },
  "/ci/recipes/set-up/monorepo-ci-azure": {
    "id": "monorepo-ci-azure",
    "name": "Setting up Azure Pipelines",
@@ -1100,14 +1111,14 @@
        "tags": []
      },
      {
-        "id": "bitbucket-cloud",
-        "name": "Enable Bitbucket Cloud PR Integration",
+        "id": "bitbucket",
+        "name": "Enable Bitbucket PR Integration",
        "description": "",
        "mediaImage": "",
-        "file": "nx-cloud/set-up/bitbucket-cloud",
+        "file": "nx-cloud/set-up/bitbucket",
        "itemList": [],
        "isExternal": false,
-        "path": "/ci/recipes/source-control-integration/bitbucket-cloud",
+        "path": "/ci/recipes/source-control-integration/bitbucket",
        "tags": []
      },
      {
@@ -1148,15 +1159,15 @@
    "path": "/ci/recipes/source-control-integration/github",
    "tags": []
  },
-  "/ci/recipes/source-control-integration/bitbucket-cloud": {
-    "id": "bitbucket-cloud",
-    "name": "Enable Bitbucket Cloud PR Integration",
+  "/ci/recipes/source-control-integration/bitbucket": {
+    "id": "bitbucket",
+    "name": "Enable Bitbucket PR Integration",
    "description": "",
    "mediaImage": "",
-    "file": "nx-cloud/set-up/bitbucket-cloud",
+    "file": "nx-cloud/set-up/bitbucket",
    "itemList": [],
    "isExternal": false,
-    "path": "/ci/recipes/source-control-integration/bitbucket-cloud",
+    "path": "/ci/recipes/source-control-integration/bitbucket",
    "tags": []
  },
  "/ci/recipes/source-control-integration/gitlab": {
@@ -1195,6 +1206,17 @@
        "mediaImage": "",
        "file": "",
        "itemList": [
+          {
+            "id": "on-premise",
+            "name": "Set up Nx Cloud On-Premise",
+            "description": "Set up Nx Cloud on machines that you control",
+            "mediaImage": "",
+            "file": "nx-cloud/features/nx-enterprise-on-prem",
+            "itemList": [],
+            "isExternal": false,
+            "path": "/ci/recipes/enterprise/on-premise/on-premise",
+            "tags": ["on-premise"]
+          },
          {
            "id": "auth-single-admin",
            "name": "Authenticate with a Single Admin",
@@ -1250,6 +1272,17 @@
            "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket",
            "tags": []
          },
+          {
+            "id": "auth-bitbucket-data-center",
+            "name": "Authenticate with BitBucket Data Center",
+            "description": "",
+            "mediaImage": "",
+            "file": "nx-cloud/enterprise/on-premise/auth-bitbucket-data-center",
+            "itemList": [],
+            "isExternal": false,
+            "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket-data-center",
+            "tags": []
+          },
          {
            "id": "auth-saml",
            "name": "Authenticate via SAML",
@@ -1261,17 +1294,6 @@
            "path": "/ci/recipes/enterprise/on-premise/auth-saml",
            "tags": []
          },
-          {
-            "id": "auth-saml-managed",
-            "name": "Authenticate via SAML on Managed Version",
-            "description": "",
-            "mediaImage": "",
-            "file": "nx-cloud/enterprise/on-premise/auth-saml-managed",
-            "itemList": [],
-            "isExternal": false,
-            "path": "/ci/recipes/enterprise/on-premise/auth-saml-managed",
-            "tags": []
-          },
          {
            "id": "advanced-config",
            "name": "Advanced Configuration",
@@ -1282,6 +1304,17 @@
            "isExternal": false,
            "path": "/ci/recipes/enterprise/on-premise/advanced-config",
            "tags": []
+          },
+          {
+            "id": "custom-github-app",
+            "name": "Custom GitHub App",
+            "description": "",
+            "mediaImage": "",
+            "file": "nx-cloud/enterprise/on-premise/custom-github-app",
+            "itemList": [],
+            "isExternal": false,
+            "path": "/ci/recipes/enterprise/on-premise/custom-github-app",
+            "tags": []
          }
        ],
        "isExternal": false,
@@ -1378,6 +1411,17 @@
    "mediaImage": "",
    "file": "",
    "itemList": [
+      {
+        "id": "on-premise",
+        "name": "Set up Nx Cloud On-Premise",
+        "description": "Set up Nx Cloud on machines that you control",
+        "mediaImage": "",
+        "file": "nx-cloud/features/nx-enterprise-on-prem",
+        "itemList": [],
+        "isExternal": false,
+        "path": "/ci/recipes/enterprise/on-premise/on-premise",
+        "tags": ["on-premise"]
+      },
      {
        "id": "auth-single-admin",
        "name": "Authenticate with a Single Admin",
@@ -1433,6 +1477,17 @@
        "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket",
        "tags": []
      },
+      {
+        "id": "auth-bitbucket-data-center",
+        "name": "Authenticate with BitBucket Data Center",
+        "description": "",
+        "mediaImage": "",
+        "file": "nx-cloud/enterprise/on-premise/auth-bitbucket-data-center",
+        "itemList": [],
+        "isExternal": false,
+        "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket-data-center",
+        "tags": []
+      },
      {
        "id": "auth-saml",
        "name": "Authenticate via SAML",
@@ -1444,17 +1499,6 @@
        "path": "/ci/recipes/enterprise/on-premise/auth-saml",
        "tags": []
      },
-      {
-        "id": "auth-saml-managed",
-        "name": "Authenticate via SAML on Managed Version",
-        "description": "",
-        "mediaImage": "",
-        "file": "nx-cloud/enterprise/on-premise/auth-saml-managed",
-        "itemList": [],
-        "isExternal": false,
-        "path": "/ci/recipes/enterprise/on-premise/auth-saml-managed",
-        "tags": []
-      },
      {
        "id": "advanced-config",
        "name": "Advanced Configuration",
@@ -1465,12 +1509,34 @@
        "isExternal": false,
        "path": "/ci/recipes/enterprise/on-premise/advanced-config",
        "tags": []
+      },
+      {
+        "id": "custom-github-app",
+        "name": "Custom GitHub App",
+        "description": "",
+        "mediaImage": "",
+        "file": "nx-cloud/enterprise/on-premise/custom-github-app",
+        "itemList": [],
+        "isExternal": false,
+        "path": "/ci/recipes/enterprise/on-premise/custom-github-app",
+        "tags": []
      }
    ],
    "isExternal": false,
    "path": "/ci/recipes/enterprise/on-premise",
    "tags": []
  },
+  "/ci/recipes/enterprise/on-premise/on-premise": {
+    "id": "on-premise",
+    "name": "Set up Nx Cloud On-Premise",
+    "description": "Set up Nx Cloud on machines that you control",
+    "mediaImage": "",
+    "file": "nx-cloud/features/nx-enterprise-on-prem",
+    "itemList": [],
+    "isExternal": false,
+    "path": "/ci/recipes/enterprise/on-premise/on-premise",
+    "tags": ["on-premise"]
+  },
  "/ci/recipes/enterprise/on-premise/auth-single-admin": {
    "id": "auth-single-admin",
    "name": "Authenticate with a Single Admin",
@@ -1526,6 +1592,17 @@
    "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket",
    "tags": []
  },
+  "/ci/recipes/enterprise/on-premise/auth-bitbucket-data-center": {
+    "id": "auth-bitbucket-data-center",
+    "name": "Authenticate with BitBucket Data Center",
+    "description": "",
+    "mediaImage": "",
+    "file": "nx-cloud/enterprise/on-premise/auth-bitbucket-data-center",
+    "itemList": [],
+    "isExternal": false,
+    "path": "/ci/recipes/enterprise/on-premise/auth-bitbucket-data-center",
+    "tags": []
+  },
  "/ci/recipes/enterprise/on-premise/auth-saml": {
    "id": "auth-saml",
    "name": "Authenticate via SAML",
@@ -1537,17 +1614,6 @@
    "path": "/ci/recipes/enterprise/on-premise/auth-saml",
    "tags": []
  },
-  "/ci/recipes/enterprise/on-premise/auth-saml-managed": {
-    "id": "auth-saml-managed",
-    "name": "Authenticate via SAML on Managed Version",
-    "description": "",
-    "mediaImage": "",
-    "file": "nx-cloud/enterprise/on-premise/auth-saml-managed",
-    "itemList": [],
-    "isExternal": false,
-    "path": "/ci/recipes/enterprise/on-premise/auth-saml-managed",
-    "tags": []
-  },
  "/ci/recipes/enterprise/on-premise/advanced-config": {
    "id": "advanced-config",
    "name": "Advanced Configuration",
@@ -1559,6 +1625,17 @@
    "path": "/ci/recipes/enterprise/on-premise/advanced-config",
    "tags": []
  },
+  "/ci/recipes/enterprise/on-premise/custom-github-app": {
+    "id": "custom-github-app",
+    "name": "Custom GitHub App",
+    "description": "",
+    "mediaImage": "",
+    "file": "nx-cloud/enterprise/on-premise/custom-github-app",
+    "itemList": [],
+    "isExternal": false,
+    "path": "/ci/recipes/enterprise/on-premise/custom-github-app",
+    "tags": []
+  },
  "/ci/recipes/enterprise/dte": {
    "id": "dte",
    "name": "Custom Distributed Task Execution",
@@ -1920,6 +1997,17 @@
        "isExternal": false,
        "path": "/ci/troubleshooting/ci-execution-failed",
        "tags": []
+      },
+      {
+        "id": "explain-with-ai",
+        "name": "Explain With AI",
+        "description": "",
+        "mediaImage": "",
+        "file": "nx-cloud/troubleshooting/explain-with-ai",
+        "itemList": [],
+        "isExternal": false,
+        "path": "/ci/troubleshooting/explain-with-ai",
+        "tags": []
      }
    ],
    "isExternal": false,
@@ -1936,5 +2024,16 @@
    "isExternal": false,
    "path": "/ci/troubleshooting/ci-execution-failed",
    "tags": []
+  },
+  "/ci/troubleshooting/explain-with-ai": {
+    "id": "explain-with-ai",
+    "name": "Explain With AI",
+    "description": "",
+    "mediaImage": "",
+    "file": "nx-cloud/troubleshooting/explain-with-ai",
+    "itemList": [],
+    "isExternal": false,
+    "path": "/ci/troubleshooting/explain-with-ai",
+    "tags": []
  }
 }
--- a/Show More
+++ b/Show More