docs(docs-infra): add npm link documentation for library development

Add comprehensive guide for using npm link with Angular libraries, including required angular.json.

fixes angular#61114

Author: aparzi

adev/src/content/tools/libraries/creating-libraries.md

@@ -242,19 +242,19 @@ TypeScript path mappings should _not_ point to the library source `.ts` files.
 
 ## Linking libraries for local development
 
-This approach is useful when:
-- You need to test library changes in a consuming application outside the monorepo
-- You're working on a standalone library that needs to be tested with external projects
-- You want to develop and test without setting up monorepo tooling
+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
+local development, without relying on the monorepo workspace structure or publishing to the NPM registry.
 
-**Note**: If you're working within a monorepo setup, the standard monorepo workflow is generally more efficient as it handles linking automatically and provides better integration.
+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:
+- You are developing a standalone library and need to test changes with an external, consuming application.
+- You are testing library changes in a consuming application outside the monorepo workspace.
 
 ### Configuring the consuming application
 
 To use linked libraries, you need to configure your application's `angular.json` file with the following settings:
 
 ```json
-
 {
   "projects": {
     "your-app": {
@@ -271,87 +271,35 @@ To use linked libraries, you need to configure your application's `angular.json`
                 "vendor": true
               },
               "prebundle": {
-                "exclude": ["@your-scope/*"]
+                "exclude": [
+                  "@your-scope/*"
+                ]
+              }
+            }
+          }
+        },
+        "serve": {
+          "configurations": {
+            "development": {
+              "prebundle": {
+                "exclude": [
+                  "@your-scope/*"
+                ]
               }
             }
           }
         }
       }
     }
-  },
-  "cli": {
-    "cache": {
-      "environment": "local"
-    }
   }
 }
 ```
 
 **Configuration options explained:**
 
-- **`preserveSymlinks: true`** - Ensures Angular follows symlinks created by `npm link` instead of resolving to their original locations
-- **`sourceMap`** - Enables source maps for easier debugging of linked library code
-- **`prebundle.exclude`** - Excludes linked libraries from pre-bundling to ensure changes are detected on each rebuild. Replace `@your-scope/*` with your library scope (e.g., `@mycompany/*`) or specific library names (e.g., `["my-lib-1", "my-lib-2"]`)
-
-### Usage
-
-1. In your library project, create a global link:
-```bash
-   cd /path/to/your-library
-   npm link
-```
-
-2. In your application project, link to the library:
-```bash
-   cd /path/to/your-app
-   npm link @your-scope/your-library
-```
-
-3. Start the dev server in your application:
-```bash
-   ng serve
-```
-
-4. When making changes to your library, rebuild it:
-```bash
-   cd /path/to/your-library
-   npm run build
-   # Or use watch mode for automatic rebuilds
-   npm run build -- --watch
-```
-
-5. The application will pick up the changes on the next rebuild (dev server will auto-reload if running)
-
-### Troubleshooting
-
-If changes aren't being picked up:
-- Ensure the library is built after making changes
-- Try clearing the Angular cache: `ng cache clean`
-- Verify the symlink exists: `ls -la node_modules/@your-scope/`
-- Restart the dev server
-
-**To unlink:**
-```bash
-cd /path/to/your-app
-npm unlink @your-scope/your-library
-npm install  # Reinstalls the original package
-
-cd /path/to/your-library
-npm unlink
-```
-
-## Publishing libraries
-
-There are two distribution formats to use when publishing a library:
-
-| Distribution formats        | Details                                                                                                                                                                                                                                                                                                                                  |
-| :-------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Partial-Ivy \(recommended\) | Contains portable code that can be consumed by Ivy applications built with any version of Angular from v12 onwards.                                                                                                                                                                                                                      |
-| Full-Ivy                    | Contains private Angular Ivy instructions, which are not guaranteed to work across different versions of Angular. This format requires that the library and application are built with the _exact_ same version of Angular. This format is useful for environments where all library and application code is built directly from source. |
-
-For publishing to npm use the partial-Ivy format as it is stable between patch versions of Angular.
-
-Avoid compiling libraries with full-Ivy code if you are publishing to npm because the generated Ivy instructions are not part of Angular's public API, and so might change between patch versions.
+- `preserveSymlinks: true`: Instructs the build system to follow the symlinks created by your package manager's linking command instead of resolving to the symlink's original location. This is essential to to avoid multiple copies of the dependent node packages.
+- `sourceMap.vendor`: Enabling vendor source maps (especially `vendor: true`) for easier debugging of linked library code.
+- `prebundle.exclude`: By default, the Angular CLI can pre-bundle all node dependencies. Excluding your library's scope (e.g., @your-scope/*) ensures that the linked source code is properly watched and rebuilt when changes occur.
 
 ## Ensuring library version compatibility