From 721080aaa93d30b90ec356c12caec672cbaa93b2 Mon Sep 17 00:00:00 2001 From: til0r Date: Sat, 29 Nov 2025 15:08:01 +0100 Subject: [PATCH] docs: fix npm link URL in creating-libraries guide - Update `npm link` to the official docs URL. - Keep `pnpm link` reference intact --- adev/src/content/tools/libraries/creating-libraries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adev/src/content/tools/libraries/creating-libraries.md b/adev/src/content/tools/libraries/creating-libraries.md index 349f42c4fef..9afa8fe448e 100644 --- a/adev/src/content/tools/libraries/creating-libraries.md +++ b/adev/src/content/tools/libraries/creating-libraries.md @@ -241,7 +241,7 @@ TypeScript path mappings should _not_ point to the library source `.ts` files. ### Linking libraries for local development This section explains how to use your package manager's local linking feature -(such as [`npm link`](https://pnpm.io/cli/link) or [`pnpm link`](https://pnpm.io/cli/link)) to test a standalone Angular library with an external application during +(such as [`npm link`](https://docs.npmjs.com/cli/v11/commands/npm-link) or [`pnpm link`](https://pnpm.io/cli/link)) to test a standalone Angular library with an external application during local development, without relying on the monorepo workspace structure or publishing to the NPM registry. NOTE: If your library and application are in the same Angular workspace (a monorepo setup), the standard monorepo workflow automatically handles the linking and is generally more efficient. This local linking approach is best when: