docs(nx-dev): remove bad link

nrwl · Oct 3, 2024 · c41922e · c41922e
1 parent 588174f
commit c41922e
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 6 deletions.
diff --git a/docs/blog/2022-12-06-nx-15-3-standalone-projects-vite-task-graph-and-more.md b/docs/blog/2022-12-06-nx-15-3-standalone-projects-vite-task-graph-and-more.md
@@ -77,7 +77,7 @@ You can add another project as well, showing what the task graph looks like for
 
 {% youtube src="https://www.youtube.com/watch?v=qEaVzh-oBBc" /%}
 
-Nx is widely known as [THE developer tool](https://monorepo.tools/) people look at when it comes to implementing monorepos in the frontend space. However, a lot of the unique features that Nx ships (in particular when it comes to implementing [Integrated Monorepos](/concepts/integrated-vs-package-based)) can be beneficial even outside of the typical monorepo scenario. In particular, Nx plugin features such as code generation, pre-configured build tooling setup, and battle-tested integration with best practices tools (e.g. Cypress, Jest, ESLint, Vite, …).
+Nx is widely known as [THE developer tool](https://monorepo.tools/) people look at when it comes to implementing monorepos in the frontend space. However, a lot of the unique features that Nx ships (in particular when it comes to implementing [Integrated Monorepos](/deprecated/integrated-vs-package-based)) can be beneficial even outside of the typical monorepo scenario. In particular, Nx plugin features such as code generation, pre-configured build tooling setup, and battle-tested integration with best practices tools (e.g. Cypress, Jest, ESLint, Vite, …).
 
 But one stands out most prominently: the **ability to easily modularize** your codebase.
 

diff --git a/docs/blog/2023-05-02-nx-16-is-here.md b/docs/blog/2023-05-02-nx-16-is-here.md
@@ -69,8 +69,6 @@ Nx will handle this migration automatically via the `nx migrate` command to upda
 
 To ensure that community plugins are not broken, the `@nrwl/*` versions of these packages are deprecated but will continue to be published until Nx 17 which is scheduled for October 2023.
 
-And you can check [the docs](/recipes/other/rescope) for further details if you like!
-
 ## Deno Standalone Apps, Edge Deployment and More
 
 Nx has had support for developing Node-based backends for a while. It was a popular choice for building your BFF in a monorepo-based setup alongside your React or Angular application. [In Nx 15.7](/blog/nx-15-7-node-support-angular-lts-lockfile-pruning) we decided to expand that support and really go deep into improving the overall DX.

diff --git a/docs/blog/2023-08-24-step-by-step-guide-to-creating-an-expo-monorepo-with-nx.md b/docs/blog/2023-08-24-step-by-step-guide-to-creating-an-expo-monorepo-with-nx.md
@@ -35,10 +35,10 @@ To create a new Nx workspace, run the command `npx create-nx-workspace <workspac
 ✔ Enable distributed caching to make your CI faster · No
 ```
 
-This will create an [integrated](/concepts/integrated-vs-package-based#integrated-repos) repo. What is an integrated repo?
+This will create an [integrated](/deprecated/integrated-vs-package-based) repo. What is an integrated repo?
 
 > An integrated repo contains projects that depend on each other through standard import statements. There is typically a [single version of every dependency](/concepts/decisions/dependency-management) defined at the root.  
-> [/concepts/integrated-vs-package-based#integrated-repos](/concepts/integrated-vs-package-based#integrated-repos)
+> [/deprecated/integrated-vs-package-based](/deprecated/integrated-vs-package-based)
 
 Now, your Nx workspace should have cats and cats-e2e under the `apps` folder and an empty libs folder:
 

diff --git a/docs/blog/2023-09-18-introducing-playwright-support-for-nx.md b/docs/blog/2023-09-18-introducing-playwright-support-for-nx.md
@@ -101,7 +101,7 @@ We get a standalone Nx React app named `nx-react-playwright`:
 ![](/blog/images/2023-09-18/1*-czlvgB1lLaIHb9uuRj9Ig.avif)
 _nx repo created_
 
-What is a [standalone application](/concepts/integrated-vs-package-based#standalone-applications)? It is like an integrated monorepo setup but with just a single, root-level application. The repo has the same file structure as an app created from Create-React-App, but we can still leverage all the generators and executors and structure your application into libraries or submodules.
+What is a [standalone application](/deprecated/integrated-vs-package-based)? It is like an integrated monorepo setup but with just a single, root-level application. The repo has the same file structure as an app created from Create-React-App, but we can still leverage all the generators and executors and structure your application into libraries or submodules.
 
 ### Run E2E