@angular/cli 20.1.0-rc.0 → 20.1.0

package/lib/config/schema.json

@@ -4299,7 +4299,7 @@
         },
         "watch": {
           "type": "boolean",
-          "description": "Run build when files change."
+          "description": "Re-run tests when source files change. Defaults to `true` in TTY environments and `false` otherwise."
         },
         "debug": {
           "type": "boolean",
@@ -4354,6 +4354,13 @@
           "type": "string",
           "description": "TypeScript file that exports an array of Angular providers to use during test execution. The array must be a default export.",
           "minLength": 1
+        },
+        "setupFiles": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "A list of global setup and configuration files that are included before the test files. The application's polyfills are always included before these files. The Angular Testbed is also initialized prior to the execution of these files."
         }
       },
       "additionalProperties": false,
@@ -4616,7 +4623,8 @@
         },
         "watch": {
           "type": "boolean",
-          "description": "Run build when files change."
+          "description": "Re-run tests when source files change.",
+          "default": true
         },
         "poll": {
           "type": "number",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@angular/cli",
-  "version": "20.1.0-rc.0",
+  "version": "20.1.0",
   "description": "CLI tool for Angular",
   "main": "lib/cli/index.js",
   "bin": {
@@ -25,13 +25,13 @@
   },
   "homepage": "https://github.com/angular/angular-cli",
   "dependencies": {
-    "@angular-devkit/architect": "0.2001.0-rc.0",
-    "@angular-devkit/core": "20.1.0-rc.0",
-    "@angular-devkit/schematics": "20.1.0-rc.0",
+    "@angular-devkit/architect": "0.2001.0",
+    "@angular-devkit/core": "20.1.0",
+    "@angular-devkit/schematics": "20.1.0",
     "@inquirer/prompts": "7.6.0",
     "@listr2/prompt-adapter-inquirer": "2.0.22",
     "@modelcontextprotocol/sdk": "1.13.3",
-    "@schematics/angular": "20.1.0-rc.0",
+    "@schematics/angular": "20.1.0",
     "@yarnpkg/lockfile": "1.1.0",
     "ini": "5.0.0",
     "jsonc-parser": "3.3.1",
@@ -41,19 +41,20 @@
     "pacote": "21.0.0",
     "resolve": "1.22.10",
     "semver": "7.7.2",
-    "yargs": "18.0.0"
+    "yargs": "18.0.0",
+    "zod": "3.25.75"
   },
   "ng-update": {
     "migrations": "@schematics/angular/migrations/migration-collection.json",
     "packageGroup": {
-      "@angular/cli": "20.1.0-rc.0",
-      "@angular/build": "20.1.0-rc.0",
-      "@angular/ssr": "20.1.0-rc.0",
-      "@angular-devkit/architect": "0.2001.0-rc.0",
-      "@angular-devkit/build-angular": "20.1.0-rc.0",
-      "@angular-devkit/build-webpack": "0.2001.0-rc.0",
-      "@angular-devkit/core": "20.1.0-rc.0",
-      "@angular-devkit/schematics": "20.1.0-rc.0"
+      "@angular/cli": "20.1.0",
+      "@angular/build": "20.1.0",
+      "@angular/ssr": "20.1.0",
+      "@angular-devkit/architect": "0.2001.0",
+      "@angular-devkit/build-angular": "20.1.0",
+      "@angular-devkit/build-webpack": "0.2001.0",
+      "@angular-devkit/core": "20.1.0",
+      "@angular-devkit/schematics": "20.1.0"
     }
   },
   "packageManager": "pnpm@9.15.9",

package/src/commands/mcp/component-generation-prompt.md

@@ -0,0 +1,60 @@
+# Angular Component Generation Prompt
+
+## Role and Goal
+
+You are an expert Angular developer specializing in creating modern, high-quality components. Your goal is to generate a new Angular component based on user requirements, ensuring it follows the latest best practices and style guidelines.
+
+## Context
+
+You are operating within an existing Angular CLI project. You have access to the project's file system and can use tools to interact with the Angular CLI for code generation.
+
+## Instructions
+
+Follow these steps to fulfill the user's request:
+
+### 1. Analyze the User's Request
+
+Carefully analyze the user's instructions to extract the following details:
+
+-   **Component Name:** The desired name for the component (e.g., 'UserProfile', 'LoginFormComponent'). Use this to form the file name and selector.
+-   **Inputs/Outputs:** Any `input()` or `output()` properties the component needs.
+-   **Component Logic:** The business logic, properties, and methods to be implemented in the component's class.
+-   **Template Structure:** The HTML structure for the component's template.
+-   **Styling:** Any CSS styles or style requirements for the component.
+-   **CLI Options:** Any specific options for the `ng generate` command, such as `--style=scss`, `--skip-tests=true`, `--view-encapsulation=Emulated`, etc.
+
+### 2. Generate the Base Component
+
+You MUST generate the initial component files using the Angular CLI. Use the following methods in order of preference:
+
+**Preference 1: Use the `generate_component` tool (if available)**
+
+-   This is the preferred method.
+-   Use the details extracted from the user's request to provide the necessary parameters.
+-   Always generate a **standalone** component unless explicitly told otherwise.
+
+**Preference 2: Use the `run_shell_command` tool**
+
+-   If a dedicated `generate_component` tool is not available, fall back to using the shell command.
+-   Construct the command like this: `ng generate component <component-name> [options...]`
+-   **Default Options:** Always include `--standalone` to create a standalone component.
+-   **User-Defined Options:** Add any other options derived from the user's request.
+
+### 3. Read the Generated Files
+
+After the CLI has generated the base files, use the `read_file` tool to get the content of the newly created:
+-   Component TypeScript file (`<component-name>.component.ts`)
+-   Component template file (`<component-name>.component.html`)
+-   Component stylesheet (`<component-name>.component.css`, etc.)
+
+### 4. Modify the Code
+
+Modify the code from the generated files to implement the specific logic, template, and styling from the user's instructions. Ensure the final code is complete, correct, and adheres to the latest Angular best practices.
+
+-   **Class:** Add the required properties, `input()`/`output()` functions, methods, and other logic to the component's class.
+-   **Template:** Build the HTML structure in the template file. Use native control flow (`@if`, `@for`, `@switch`) instead of structural directives (`*ngIf`, `*ngFor`).
+-   **Stylesheet:** Add the necessary styles to the stylesheet.
+
+### 5. Final Output
+
+Present the complete, final code for each modified file. Do not show diffs or partial code snippets. The user should be able to copy and paste the code directly into their project.

package/src/commands/mcp/mcp-server.js

@@ -14,6 +14,7 @@ exports.createMcpServer = createMcpServer;
 const mcp_js_1 = require("@modelcontextprotocol/sdk/server/mcp.js");
 const promises_1 = require("node:fs/promises");
 const node_path_1 = __importDefault(require("node:path"));
+const zod_1 = require("zod");
 const version_1 = require("../../utilities/version");
 async function createMcpServer(context) {
     const server = new mcp_js_1.McpServer({
@@ -25,36 +26,80 @@ async function createMcpServer(context) {
         },
     });
     server.registerResource('instructions', 'instructions://best-practices', {
-        title: 'Angular System Instructions',
-        description: 'A set of instructions to help LLMs generate correct code that follows Angular best practices.',
+        title: 'Angular Best Practices and Code Generation Guide',
+        description: "A comprehensive guide detailing Angular's best practices for code generation and development." +
+            ' This guide should be used as a reference by an LLM to ensure any generated code' +
+            ' adheres to modern Angular standards, including the use of standalone components,' +
+            ' typed forms, modern control flow syntax, and other current conventions.',
         mimeType: 'text/markdown',
     }, async () => {
         const text = await (0, promises_1.readFile)(node_path_1.default.join(__dirname, 'instructions', 'best-practices.md'), 'utf-8');
         return { contents: [{ uri: 'instructions://best-practices', text }] };
     });
     server.registerTool('list_projects', {
-        title: 'List projects',
-        description: 'List projects within an Angular workspace.' +
-            ' This information is read from the `angular.json` file at the root path of the Angular workspace',
-    }, () => {
-        if (!context.workspace) {
+        title: 'List Angular Projects',
+        description: 'Lists the names of all applications and libraries defined within an Angular workspace. ' +
+            'It reads the `angular.json` configuration file to identify the projects. ',
+        annotations: {
+            readOnlyHint: true,
+        },
+        outputSchema: {
+            projects: zod_1.z.array(zod_1.z.object({
+                name: zod_1.z
+                    .string()
+                    .describe('The name of the project, as defined in the `angular.json` file.'),
+                type: zod_1.z
+                    .enum(['application', 'library'])
+                    .optional()
+                    .describe(`The type of the project, either 'application' or 'library'.`),
+                root: zod_1.z
+                    .string()
+                    .describe('The root directory of the project, relative to the workspace root.'),
+                sourceRoot: zod_1.z
+                    .string()
+                    .describe(`The root directory of the project's source files, relative to the workspace root.`),
+                selectorPrefix: zod_1.z
+                    .string()
+                    .optional()
+                    .describe('The prefix to use for component selectors.' +
+                    ` For example, a prefix of 'app' would result in selectors like '<app-my-component>'.`),
+            })),
+        },
+    }, async () => {
+        const { workspace } = context;
+        if (!workspace) {
             return {
                 content: [
                     {
                         type: 'text',
-                        text: 'Not within an Angular project.',
+                        text: 'No Angular workspace found.' +
+                            ' An `angular.json` file, which marks the root of a workspace,' +
+                            ' could not be located in the current directory or any of its parent directories.',
                     },
                 ],
             };
         }
+        const projects = [];
+        // Convert to output format
+        for (const [name, project] of workspace.projects.entries()) {
+            projects.push({
+                name,
+                type: project.extensions['projectType'],
+                root: project.root,
+                sourceRoot: project.sourceRoot ?? node_path_1.default.posix.join(project.root, 'src'),
+                selectorPrefix: project.extensions['prefix'],
+            });
+        }
+        // The structuredContent field is newer and may not be supported by all hosts.
+        // A text representation of the content is also provided for compatibility.
         return {
             content: [
                 {
                     type: 'text',
-                    text: 'Projects in the Angular workspace: ' +
-                        [...context.workspace.projects.keys()].join(','),
+                    text: `Projects in the Angular workspace:\n${JSON.stringify(projects)}`,
                 },
             ],
+            structuredContent: { projects },
         };
     });
     return server;

package/src/utilities/version.js

@@ -22,4 +22,4 @@ class Version {
         this.patch = patch;
     }
 }
-exports.VERSION = new Version('20.1.0-rc.0');
+exports.VERSION = new Version('20.1.0');