@angular/material - npm Package Compare versions

Comparing version 20.1.1 to 20.1.2

package.json

 {
   "name": "@angular/material",
-  "version": "20.1.1",
+  "version": "20.1.2",
   "description": "Angular Material",
@@ -356,3 +356,3 @@ "repository": {
   "peerDependencies": {
-    "@angular/cdk": "20.1.1",
+    "@angular/cdk": "20.1.2",
     "@angular/core": "^20.0.0 || ^21.0.0",
@@ -359,0 +359,0 @@ "@angular/common": "^20.0.0 || ^21.0.0",

schematics/ng-add/index.js

@@ -22,3 +22,3 @@ "use strict";
  */
-const fallbackMaterialVersionRange = `~20.1.1`;
+const fallbackMaterialVersionRange = `~20.1.2`;
 /**
@@ -25,0 +25,0 @@ * Schematic factory entry-point for the `ng-add` schematic. The ng-add schematic will be

schematics/ng-add/theming/theming.js

@@ -25,3 +25,10 @@ "use strict";
     return (host, context) => {
-        const palettes = options.theme || 'azure-blue';
+        let palettes = options.theme || 'azure-blue';
+        // For a long time, theme param could be "custom" which meant to add a custom theme. This option
+        // was removed since we always add a custom theme, and we expect this option to be the
+        // user's preferred palettes. However it's possible that users will have hardcoded CLI commands
+        // that pass "--theme custom" and we can gracefully handle this by assuming azure-blue.
+        if (palettes === 'custom') {
+            palettes = 'azure-blue';
+        }
         return insertCustomTheme(palettes, options.project, host, context.logger);
@@ -28,0 +35,0 @@ };

No alert changes

Improved metrics

Total package byte prevSize

8511463

0.01%

Lines of code

76977

0.01%

No dependency changes