@angular/cli 20.1.2 → 20.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@angular/cli",
-  "version": "20.1.2",
+  "version": "20.1.4",
   "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.2",
-    "@angular-devkit/core": "20.1.2",
-    "@angular-devkit/schematics": "20.1.2",
+    "@angular-devkit/architect": "0.2001.4",
+    "@angular-devkit/core": "20.1.4",
+    "@angular-devkit/schematics": "20.1.4",
     "@inquirer/prompts": "7.6.0",
     "@listr2/prompt-adapter-inquirer": "2.0.22",
     "@modelcontextprotocol/sdk": "1.13.3",
-    "@schematics/angular": "20.1.2",
+    "@schematics/angular": "20.1.4",
     "@yarnpkg/lockfile": "1.1.0",
     "algoliasearch": "5.32.0",
     "ini": "5.0.0",
@@ -48,14 +48,14 @@
   "ng-update": {
     "migrations": "@schematics/angular/migrations/migration-collection.json",
     "packageGroup": {
-      "@angular/cli": "20.1.2",
-      "@angular/build": "20.1.2",
-      "@angular/ssr": "20.1.2",
-      "@angular-devkit/architect": "0.2001.2",
-      "@angular-devkit/build-angular": "20.1.2",
-      "@angular-devkit/build-webpack": "0.2001.2",
-      "@angular-devkit/core": "20.1.2",
-      "@angular-devkit/schematics": "20.1.2"
+      "@angular/cli": "20.1.4",
+      "@angular/build": "20.1.4",
+      "@angular/ssr": "20.1.4",
+      "@angular-devkit/architect": "0.2001.4",
+      "@angular-devkit/build-angular": "20.1.4",
+      "@angular-devkit/build-webpack": "0.2001.4",
+      "@angular-devkit/core": "20.1.4",
+      "@angular-devkit/schematics": "20.1.4"
     }
   },
   "packageManager": "pnpm@9.15.9",

package/src/commands/mcp/instructions/best-practices.md

@@ -9,10 +9,12 @@ You are an expert in TypeScript, Angular, and scalable web application developme
 ## Angular Best Practices
 
 - Always use standalone components over NgModules
-- Don't use explicit `standalone: true` (it is implied by default)
+- Must NOT set `standalone: true` inside Angular decorators. It's the default.
 - Use signals for state management
 - Implement lazy loading for feature routes
+- Do NOT use the `@HostBinding` and `@HostListener` decorators. Put host bindings inside the `host` object of the `@Component` or `@Directive` decorator instead
 - Use `NgOptimizedImage` for all static images.
+  - `NgOptimizedImage` does not work for inline base64 images.
 
 ## Components
 
@@ -30,6 +32,7 @@ You are an expert in TypeScript, Angular, and scalable web application developme
 - Use signals for local component state
 - Use `computed()` for derived state
 - Keep state transformations pure and predictable
+- Do NOT use `mutate` on signals, use `update` or `set` instead
 
 ## Templates
 
@@ -42,3 +45,8 @@ You are an expert in TypeScript, Angular, and scalable web application developme
 - Design services around a single responsibility
 - Use the `providedIn: 'root'` option for singleton services
 - Use the `inject()` function instead of constructor injection
+
+## Common pitfalls
+
+- Control flow (`@if`):
+  - You cannot use `as` expressions in `@else if (...)`. E.g. invalid code: `@else if (bla(); as x)`.

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

@@ -39,7 +39,11 @@ async function createMcpServer(context) {
         return { contents: [{ uri: 'instructions://best-practices', text }] };
     });
     (0, best_practices_1.registerBestPracticesTool)(server);
-    (0, projects_1.registerListProjectsTool)(server, context);
+    // If run outside an Angular workspace (e.g., globally) skip the workspace specific tools.
+    // Currently only the `list_projects` tool.
+    if (!context.workspace) {
+        (0, projects_1.registerListProjectsTool)(server, context);
+    }
     await (0, doc_search_1.registerDocSearchTool)(server);
     return server;
 }

package/src/utilities/version.js

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