docs(misc): fix blog posts for nx 21 (#31155)

<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->

<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #
This commit is contained in:
Mike Hartington 2025-05-09 14:49:06 -04:00 committed by GitHub
parent 0a2553aa2c
commit 8082184dc7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 7 additions and 7 deletions

View File

@ -16,8 +16,8 @@ This article is part of the Nx 21 Launch Week series:
- **Nx 21 Release: Continuous tasks and Terminal UI lead the way** - **Nx 21 Release: Continuous tasks and Terminal UI lead the way**
- [Introducing Migrate UI in Nx Console](/blog/migrate-ui) - [Introducing Migrate UI in Nx Console](/blog/migrate-ui)
- [New and Improved Module Federation Experience](/blog/improved-module-federation) - [New and Improved Module Federation Experience](/blog/improved-module-federation)
- Continuous tasks are a huge DX improvement - [Continuous tasks are a huge DX improvement](/blog/nx-21-continuous-tasks)
- A New UI For The Humble Terminal - [A New UI For The Humble Terminal](/blog/nx-21-terminal-ui)
{% /callout %} {% /callout %}

View File

@ -16,8 +16,8 @@ This article is part of the Nx 21 Launch Week series:
- [Nx 21 Release: Continuous tasks and Terminal UI lead the way](/blog/nx-21-release) - [Nx 21 Release: Continuous tasks and Terminal UI lead the way](/blog/nx-21-release)
- **Introducing Migrate UI in Nx Console** - **Introducing Migrate UI in Nx Console**
- [New and Improved Module Federation Experience](/blog/improved-module-federation) - [New and Improved Module Federation Experience](/blog/improved-module-federation)
- Continuous tasks are a huge DX improvement - [Continuous tasks are a huge DX improvement](/blog/nx-21-continuous-tasks)
- A New UI For The Humble Terminal - [A New UI For The Humble Terminal](/blog/nx-21-terminal-ui)
{% /callout %} {% /callout %}

View File

@ -13,8 +13,8 @@ pinned: true
- [Nx 21 Release: Continuous tasks and Terminal UI lead the way](/blog/nx-21-release) - [Nx 21 Release: Continuous tasks and Terminal UI lead the way](/blog/nx-21-release)
- [Introducing Migrate UI in Nx Console](/blog/migrate-ui) - [Introducing Migrate UI in Nx Console](/blog/migrate-ui)
- **New and Improved Module Federation Experience** - **New and Improved Module Federation Experience**
- Continuous tasks are a huge DX improvement - [Continuous tasks are a huge DX improvement](/blog/nx-21-continuous-tasks)
- A New UI For The Humble Terminal - [A New UI For The Humble Terminal](/blog/nx-21-terminal-ui)
{% /callout %} {% /callout %}

View File

@ -33,7 +33,7 @@ Great question! Why spend time on a terminal? Well, the terminal is the starting
Let's first look at how the terminal behaves in Nx 20 and below. In a project with multiple packages, if you run `nx run-many`, what you'll first notice is that you get all the output from any continuous tasks mixed together in one giant stream. This is very typical in most terminal programs, but with monorepos it's not ideal. For instance, let's say we have a build error in one of our projects: Let's first look at how the terminal behaves in Nx 20 and below. In a project with multiple packages, if you run `nx run-many`, what you'll first notice is that you get all the output from any continuous tasks mixed together in one giant stream. This is very typical in most terminal programs, but with monorepos it's not ideal. For instance, let's say we have a build error in one of our projects:
{% video-player src="/documentation/blog/media/2025-05-09/old-tui.mp4" alt="Showing the previous terminal experience for Nx" autoPlay=true loop=true /%} {% video-player src="/documentation/blog/media/2025-05-07/old-tui.mp4" alt="Showing the previous terminal experience for Nx" autoPlay=true loop=true /%}
It might be hard to notice that we had the error if we have multiple tasks being run, so unless we scroll up, we could miss it. This might sound trivial, but it's an annoyance that doesn't have to happen. It's also difficult to separate tasks that are continuous and those that have an ending. It might be hard to notice that we had the error if we have multiple tasks being run, so unless we scroll up, we could miss it. This might sound trivial, but it's an annoyance that doesn't have to happen. It's also difficult to separate tasks that are continuous and those that have an ending.