fix(nx-dev): 404 urls (#27599)

This commit is contained in:
Nicholas Cunningham 2024-10-01 08:40:35 -06:00 committed by GitHub
parent 27edf71cef
commit c5bb723ed7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 4 additions and 4 deletions

View File

@ -31,7 +31,7 @@ If you prefer diagrams, the one below outlines the above steps.
Previously, when using shared workspace libraries as part of your Module Federation application, there was a chance that the workspace library would be provided by one of the `static remotes`. This would cause issues where changes to those shared libraries would not be reflected in the locally served application. Previously, when using shared workspace libraries as part of your Module Federation application, there was a chance that the workspace library would be provided by one of the `static remotes`. This would cause issues where changes to those shared libraries would not be reflected in the locally served application.
To combat this issue, we developed the `NxRuntimeLibraryControlPlugin`. This is a [Runtime Plugin]() that will ensure that workspace libraries are only shared via any active `dev remote`. This means that any changes to the shared library will be picked up by `webpack-dev-server` and, as such, reflected in the locally served application. To combat this issue, we developed the `NxRuntimeLibraryControlPlugin`. This is a _Runtime Plugin_ that will ensure that workspace libraries are only shared via any active `dev remote`. This means that any changes to the shared library will be picked up by `webpack-dev-server` and, as such, reflected in the locally served application.
This plugin is enabled by default, however, you can turn it off in your `module-federation.config` file: This plugin is enabled by default, however, you can turn it off in your `module-federation.config` file:

View File

@ -2,7 +2,7 @@
Nx Plugins can be used to easily integrate a tool or framework into an Nx repository. If there is no plugin available for your favorite tool or framework, you can write your own. Nx Plugins can be used to easily integrate a tool or framework into an Nx repository. If there is no plugin available for your favorite tool or framework, you can write your own.
In this tutorial, we'll create a plugin that helps to integrate the [Astro]() framework. `Astro` is a JavaScript web framework optimized for building fast, content-driven websites. We'll call our plugin `nx-astro`. In this tutorial, we'll create a plugin that helps to integrate the _Astro_ framework. `Astro` is a JavaScript web framework optimized for building fast, content-driven websites. We'll call our plugin `nx-astro`.
To create a plugin in a brand new repository, use the `create-nx-plugin` command: To create a plugin in a brand new repository, use the `create-nx-plugin` command:

View File

@ -531,7 +531,7 @@ export function SmarterToolsForMonorepos(): JSX.Element {
</Card> </Card>
<Card> <Card>
<Link <Link
href="/nx-api/rspac?utm_medium=website&utm_campaign=homepage_links&utm_content=cta_smarter_tools_techlink" href="/nx-api/rspack?utm_medium=website&utm_campaign=homepage_links&utm_content=cta_smarter_tools_techlink"
prefetch={false} prefetch={false}
title="Nx with RSpack" title="Nx with RSpack"
className="h-full w-full p-2 sm:p-4" className="h-full w-full p-2 sm:p-4"

View File

@ -84,7 +84,7 @@ export function HobbyPlan({
/> />
<p> <p>
<Link <Link
href="/ci/features/agents" href="/ci/features/distribute-task-execution"
title="Learn more about Nx Agents" title="Learn more about Nx Agents"
prefetch={false} prefetch={false}
className="font-medium text-slate-700 underline dark:text-slate-300" className="font-medium text-slate-700 underline dark:text-slate-300"