@schematics/angular 19.1.0-rc.0 → 19.1.0

package/ng-new/schema.json

@@ -3,15 +3,15 @@
   "$id": "SchematicsAngularNgNew",
   "title": "Angular Ng New Options Schema",
   "type": "object",
-  "description": "Creates a new project by combining the workspace and application schematics.",
+  "description": "Creates a new Angular workspace and an initial project. This schematic sets up the foundation for your Angular development, generating the workspace configuration files and an optional starter application. You can customize various aspects of the workspace and the initial project, such as routing, styling, and testing.",
   "additionalProperties": false,
   "properties": {
     "directory": {
       "type": "string",
-      "description": "The directory name to create the workspace in."
+      "description": "The directory where the new workspace and project should be created. If not specified, the workspace will be created in the current directory."
     },
     "name": {
-      "description": "The name of the new workspace and initial project.",
+      "description": "The name for the new workspace and the initial project. This name will be used for the root directory and various identifiers throughout the project.",
       "type": "string",
       "$default": {
         "$source": "argv",
@@ -20,18 +20,18 @@
       "x-prompt": "What name would you like to use for the new workspace and initial project?"
     },
     "skipInstall": {
-      "description": "Do not install dependency packages.",
+      "description": "Skip the automatic installation of packages. You will need to manually install the dependencies later.",
       "type": "boolean",
       "default": false
     },
     "skipGit": {
-      "description": "Do not initialize a git repository.",
+      "description": "Do not initialize a Git repository in the new workspace. By default, a Git repository is initialized to help you track changes to your project.",
       "type": "boolean",
       "default": false,
       "alias": "g"
     },
     "commit": {
-      "description": "Initial git repository commit information.",
+      "description": "Configure the initial Git commit for the new repository.",
       "oneOf": [
         { "type": "boolean" },
         {
@@ -54,24 +54,24 @@
       "default": true
     },
     "newProjectRoot": {
-      "description": "The path where new projects will be created, relative to the new workspace root.",
+      "description": "The path where new projects will be created within the workspace, relative to the workspace root. By default, new projects are created in the `projects` directory.",
       "type": "string",
       "default": "projects"
     },
     "inlineStyle": {
-      "description": "Include styles inline in the component TS file. By default, an external styles file is created and referenced in the component TypeScript file.",
+      "description": "Include the styles for the initial application's root component directly within the `app.component.ts` file. By default, a separate stylesheet file (e.g., `app.component.css`) is created.",
       "type": "boolean",
       "alias": "s",
       "x-user-analytics": "ep.ng_inline_style"
     },
     "inlineTemplate": {
-      "description": "Include template inline in the component TS file. By default, an external template file is created and referenced in the component TypeScript file.",
+      "description": "Include the HTML template for the initial application's root component directly within the `app.component.ts` file. By default, a separate template file (e.g., `app.component.html`) is created.",
       "type": "boolean",
       "alias": "t",
       "x-user-analytics": "ep.ng_inline_template"
     },
     "viewEncapsulation": {
-      "description": "The view encapsulation strategy to use in the initial project.",
+      "description": "Sets the view encapsulation mode for components in the initial project. This determines how component styles are scoped and applied. Options include: `Emulated` (default, styles are scoped to the component), `None` (styles are global), and `ShadowDom` (styles are encapsulated using Shadow DOM).",
       "enum": ["Emulated", "None", "ShadowDom"],
       "type": "string"
     },
@@ -85,41 +85,41 @@
     },
     "routing": {
       "type": "boolean",
-      "description": "Enable routing in the initial project.",
+      "description": "Enable routing in the initial application project. This sets up the necessary files and modules for managing navigation between different views in your application.",
       "x-user-analytics": "ep.ng_routing"
     },
     "prefix": {
       "type": "string",
       "format": "html-selector",
-      "description": "The prefix to apply to generated selectors for the initial project.",
+      "description": "The prefix to apply to generated selectors for the initial project. For example, if the prefix is `my-app` and you generate a component named `my-component`, the selector will be `my-app-my-component`.",
       "minLength": 1,
       "default": "app",
       "alias": "p"
     },
     "style": {
-      "description": "The file extension or preprocessor to use for style files.",
+      "description": "The type of stylesheet files to be created for components in the initial project.",
       "type": "string",
       "enum": ["css", "scss", "sass", "less"],
       "x-user-analytics": "ep.ng_style"
     },
     "skipTests": {
-      "description": "Do not generate \"spec.ts\" test files for the new project.",
+      "description": "Skip the generation of unit test files `spec.ts`.",
       "type": "boolean",
       "default": false,
       "alias": "S"
     },
     "createApplication": {
-      "description": "Create a new initial application project in the 'src' folder of the new workspace. When false, creates an empty workspace with no initial application. You can then use the generate application command so that all applications are created in the projects folder.",
+      "description": "Create a new initial application project in the new workspace. When false, creates an empty workspace with no initial application. You can then use the `ng generate application` command to create applications in the `projects` directory.",
       "type": "boolean",
       "default": true
     },
     "minimal": {
-      "description": "Create a workspace without any testing frameworks. (Use for learning purposes only.)",
+      "description": "Generate a minimal Angular workspace without any testing frameworks. This is intended for learning purposes and simple experimentation, not for production applications.",
       "type": "boolean",
       "default": false
     },
     "strict": {
-      "description": "Creates a workspace with stricter type checking and stricter bundle budgets settings. This setting helps improve maintainability and catch bugs ahead of time. For more information, see https://angular.dev/tools/cli/template-typecheck#strict-mode",
+      "description": "Enable stricter type checking and stricter bundle budgets settings. This setting helps improve maintainability and catch bugs ahead of time. For more information, see https://angular.dev/tools/cli/template-typecheck#strict-mode",
       "type": "boolean",
       "default": true
     },
@@ -135,16 +135,16 @@
       "x-user-analytics": "ep.ng_standalone"
     },
     "ssr": {
-      "description": "Creates an application with Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering) enabled.",
+      "description": "Configure the initial application for Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering).",
       "type": "boolean",
       "x-user-analytics": "ep.ng_ssr"
     },
     "serverRouting": {
-      "description": "Creates a server application using the Server Routing and App Engine APIs (Developer Preview).",
+      "description": "Create a server application in the initial project using the Server Routing and App Engine APIs (Developer Preview).",
       "type": "boolean"
     },
     "experimentalZoneless": {
-      "description": "Create an application that does not utilize zone.js.",
+      "description": "Create an initial application that does not utilize `zone.js`.",
       "type": "boolean",
       "default": false
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@schematics/angular",
-  "version": "19.1.0-rc.0",
+  "version": "19.1.0",
   "description": "Schematics specific to Angular",
   "homepage": "https://github.com/angular/angular-cli",
   "keywords": [
@@ -22,8 +22,8 @@
   },
   "schematics": "./collection.json",
   "dependencies": {
-    "@angular-devkit/core": "19.1.0-rc.0",
-    "@angular-devkit/schematics": "19.1.0-rc.0",
+    "@angular-devkit/core": "19.1.0",
+    "@angular-devkit/schematics": "19.1.0",
     "jsonc-parser": "3.3.1"
   },
   "repository": {

package/pipe/schema.d.ts

@@ -1,41 +1,52 @@
 /**
- * Creates a new, generic pipe definition in the given project.
+ * Creates a new pipe in your project. Pipes are used to transform data for display in
+ * templates. They take input values and apply a specific transformation, such as formatting
+ * dates, currency, or filtering arrays. This schematic generates the necessary files and
+ * boilerplate code for a new pipe.
  */
 export interface Schema {
     /**
-     * The declaring NgModule exports this pipe.
+     * Automatically export the pipe from the specified NgModule, making it accessible to other
+     * modules in the application.
      */
     export?: boolean;
     /**
-     * When true (the default) creates files at the top level of the project.
+     * Creates the new pipe files at the top level of the current project. If set to false, a
+     * new folder with the pipe's name will be created to contain the files.
      */
     flat?: boolean;
     /**
-     * The declaring NgModule.
+     * Specify the NgModule where the pipe should be declared. If not provided, the CLI will
+     * attempt to find the closest NgModule in the pipe's path.
      */
     module?: string;
     /**
-     * The name of the pipe.
+     * The name for the new pipe. This will be used to create the pipe's class and spec files
+     * (e.g., `my-pipe.pipe.ts` and `my-pipe.pipe.spec.ts`).
      */
     name: string;
     /**
-     * The path at which to create the pipe, relative to the workspace root.
+     * The path where the pipe files should be created, relative to the workspace root. If not
+     * provided, the pipe will be created in the current directory.
      */
     path?: string;
     /**
-     * The name of the project.
+     * The name of the project where the pipe should be created. If not specified, the CLI will
+     * determine the project from the current directory.
      */
     project: string;
     /**
-     * Do not import this pipe into the owning NgModule.
+     * Do not automatically import the new pipe into its closest NgModule.
      */
     skipImport?: boolean;
     /**
-     * Do not create "spec.ts" test files for the new pipe.
+     * Prevent the generation of a unit test file `spec.ts` for the new pipe.
      */
     skipTests?: boolean;
     /**
-     * Whether the generated pipe is standalone.
+     * Generate a standalone pipe. Standalone pipes are self-contained and don't need to be
+     * declared in an NgModule. They can be used independently or imported directly into other
+     * standalone components, directives, or pipes.
      */
     standalone?: boolean;
 }

package/pipe/schema.json

@@ -4,11 +4,11 @@
   "title": "Angular Pipe Options Schema",
   "type": "object",
   "additionalProperties": false,
-  "description": "Creates a new, generic pipe definition in the given project.",
+  "description": "Creates a new pipe in your project. Pipes are used to transform data for display in templates. They take input values and apply a specific transformation, such as formatting dates, currency, or filtering arrays. This schematic generates the necessary files and boilerplate code for a new pipe.",
   "properties": {
     "name": {
       "type": "string",
-      "description": "The name of the pipe.",
+      "description": "The name for the new pipe. This will be used to create the pipe's class and spec files (e.g., `my-pipe.pipe.ts` and `my-pipe.pipe.spec.ts`).",
       "$default": {
         "$source": "argv",
         "index": 0
@@ -21,12 +21,12 @@
       "$default": {
         "$source": "workingDirectory"
       },
-      "description": "The path at which to create the pipe, relative to the workspace root.",
+      "description": "The path where the pipe files should be created, relative to the workspace root. If not provided, the pipe will be created in the current directory.",
       "visible": false
     },
     "project": {
       "type": "string",
-      "description": "The name of the project.",
+      "description": "The name of the project where the pipe should be created. If not specified, the CLI will determine the project from the current directory.",
       "$default": {
         "$source": "projectName"
       }
@@ -34,33 +34,33 @@
     "flat": {
       "type": "boolean",
       "default": true,
-      "description": "When true (the default) creates files at the top level of the project."
+      "description": "Creates the new pipe files at the top level of the current project. If set to false, a new folder with the pipe's name will be created to contain the files."
     },
     "skipTests": {
       "type": "boolean",
-      "description": "Do not create \"spec.ts\" test files for the new pipe.",
+      "description": "Prevent the generation of a unit test file `spec.ts` for the new pipe.",
       "default": false
     },
     "skipImport": {
       "type": "boolean",
       "default": false,
-      "description": "Do not import this pipe into the owning NgModule."
+      "description": "Do not automatically import the new pipe into its closest NgModule."
     },
     "standalone": {
-      "description": "Whether the generated pipe is standalone.",
+      "description": "Generate a standalone pipe. Standalone pipes are self-contained and don't need to be declared in an NgModule. They can be used independently or imported directly into other standalone components, directives, or pipes.",
       "type": "boolean",
       "default": true,
       "x-user-analytics": "ep.ng_standalone"
     },
     "module": {
       "type": "string",
-      "description": "The declaring NgModule.",
+      "description": "Specify the NgModule where the pipe should be declared. If not provided, the CLI will attempt to find the closest NgModule in the pipe's path.",
       "alias": "m"
     },
     "export": {
       "type": "boolean",
       "default": false,
-      "description": "The declaring NgModule exports this pipe."
+      "description": "Automatically export the pipe from the specified NgModule, making it accessible to other modules in the application."
     }
   },
   "required": ["name", "project"]

package/resolver/schema.d.ts

@@ -1,30 +1,37 @@
 /**
- * Generates a new, generic resolver definition in the given project.
+ * Creates a new resolver in your project. Resolvers are used to pre-fetch data before a
+ * route is activated, ensuring that the necessary data is available before the component is
+ * displayed. This can improve the user experience by preventing delays and loading states.
+ * This schematic generates a new resolver with the specified name and options.
  */
 export interface Schema {
     /**
-     * When true (the default), creates the new files at the top level of the current project.
+     * Creates the new resolver files at the top level of the current project. If set to false,
+     * a new folder with the resolver's name will be created to contain the files.
      */
     flat?: boolean;
     /**
-     * Creates the resolver as a `ResolveFn`.
+     * Creates the resolver as a function `ResolveFn` instead of a class. Functional resolvers
+     * can be simpler for basic scenarios.
      */
     functional?: boolean;
     /**
-     * The name of the new resolver.
+     * The name for the new resolver. This will be used to create the resolver's class and spec
+     * files (e.g., `my-resolver.resolver.ts` and `my-resolver.resolver.spec.ts`).
      */
     name: string;
     /**
-     * The path at which to create the interface that defines the resolver, relative to the
-     * current workspace.
+     * The path where the resolver files should be created, relative to the current workspace.
+     * If not provided, the resolver will be created in the current directory.
      */
     path?: string;
     /**
-     * The name of the project.
+     * The name of the project where the resolver should be created. If not specified, the CLI
+     * will determine the project from the current directory.
      */
     project: string;
     /**
-     * Do not create "spec.ts" test files for the new resolver.
+     * Skip the generation of a unit test file `spec.ts` for the new resolver.
      */
     skipTests?: boolean;
 }

package/resolver/schema.json

@@ -1,14 +1,14 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "SchematicsAngularResolver",
-  "title": "Angular resolver Options Schema",
+  "title": "Angular Resolver Options Schema",
   "type": "object",
   "additionalProperties": false,
-  "description": "Generates a new, generic resolver definition in the given project.",
+  "description": "Creates a new resolver in your project. Resolvers are used to pre-fetch data before a route is activated, ensuring that the necessary data is available before the component is displayed. This can improve the user experience by preventing delays and loading states. This schematic generates a new resolver with the specified name and options.",
   "properties": {
     "name": {
       "type": "string",
-      "description": "The name of the new resolver.",
+      "description": "The name for the new resolver. This will be used to create the resolver's class and spec files (e.g., `my-resolver.resolver.ts` and `my-resolver.resolver.spec.ts`).",
       "$default": {
         "$source": "argv",
         "index": 0
@@ -17,17 +17,17 @@
     },
     "skipTests": {
       "type": "boolean",
-      "description": "Do not create \"spec.ts\" test files for the new resolver.",
+      "description": "Skip the generation of a unit test file `spec.ts` for the new resolver.",
       "default": false
     },
     "flat": {
       "type": "boolean",
-      "description": "When true (the default), creates the new files at the top level of the current project.",
+      "description": "Creates the new resolver files at the top level of the current project. If set to false, a new folder with the resolver's name will be created to contain the files.",
       "default": true
     },
     "functional": {
       "type": "boolean",
-      "description": "Creates the resolver as a `ResolveFn`.",
+      "description": "Creates the resolver as a function `ResolveFn` instead of a class. Functional resolvers can be simpler for basic scenarios.",
       "default": true
     },
     "path": {
@@ -36,12 +36,12 @@
       "$default": {
         "$source": "workingDirectory"
       },
-      "description": "The path at which to create the interface that defines the resolver, relative to the current workspace.",
+      "description": "The path where the resolver files should be created, relative to the current workspace. If not provided, the resolver will be created in the current directory.",
       "visible": false
     },
     "project": {
       "type": "string",
-      "description": "The name of the project.",
+      "description": "The name of the project where the resolver should be created. If not specified, the CLI will determine the project from the current directory.",
       "$default": {
         "$source": "projectName"
       }

package/server/schema.d.ts

@@ -1,18 +1,21 @@
 /**
- * Pass this schematic to the "run" command to set up server-side rendering for an app.
+ * Sets up server-side rendering (SSR) for your Angular application. SSR allows your app to
+ * be rendered on the server, improving initial load performance and SEO. This schematic
+ * configures your project for SSR and generates the necessary files.
  */
 export interface Schema {
     /**
-     * The name of the project.
+     * The name of the project to enable server-side rendering for.
      */
     project: string;
     /**
-     * Creates a server application using the Server Routing and App Engine APIs (Developer
+     * Configure the server application to use the Server Routing and App Engine APIs (Developer
      * Preview).
      */
     serverRouting?: boolean;
     /**
-     * Do not install packages for dependencies.
+     * Skip the automatic installation of packages. You will need to manually install the
+     * dependencies later.
      */
     skipInstall?: boolean;
 }

package/server/schema.json

@@ -4,22 +4,22 @@
   "title": "Angular Server App Options Schema",
   "type": "object",
   "additionalProperties": false,
-  "description": "Pass this schematic to the \"run\" command to set up server-side rendering for an app.",
+  "description": "Sets up server-side rendering (SSR) for your Angular application. SSR allows your app to be rendered on the server, improving initial load performance and SEO. This schematic configures your project for SSR and generates the necessary files.",
   "properties": {
     "project": {
       "type": "string",
-      "description": "The name of the project.",
+      "description": "The name of the project to enable server-side rendering for.",
       "$default": {
         "$source": "projectName"
       }
     },
     "skipInstall": {
-      "description": "Do not install packages for dependencies.",
+      "description": "Skip the automatic installation of packages. You will need to manually install the dependencies later.",
       "type": "boolean",
       "default": false
     },
     "serverRouting": {
-      "description": "Creates a server application using the Server Routing and App Engine APIs (Developer Preview).",
+      "description": "Configure the server application to use the Server Routing and App Engine APIs (Developer Preview).",
       "type": "boolean"
     }
   },

package/service/schema.d.ts

@@ -1,25 +1,31 @@
 /**
- * Creates a new, generic service definition in the given project.
+ * Creates a new service in your project. Services are used to encapsulate reusable logic,
+ * such as data access, API calls, or utility functions. This schematic simplifies the
+ * process of generating a new service with the necessary files and boilerplate code.
  */
 export interface Schema {
     /**
-     * When true (the default), creates files at the top level of the project.
+     * Creates files at the top level of the project or the given path. If set to false, a new
+     * folder with the service's name will be created to contain the files.
      */
     flat?: boolean;
     /**
-     * The name of the service.
+     * The name for the new service. This will be used to create the service's class and spec
+     * files (e.g., `my-service.service.ts` and `my-service.service.spec.ts`).
      */
     name: string;
     /**
-     * The path at which to create the service, relative to the workspace root.
+     * The path where the service files should be created, relative to the workspace root. If
+     * not provided, the service will be created in the project's `src/app` directory.
      */
     path?: string;
     /**
-     * The name of the project.
+     * The name of the project where the service should be added. If not specified, the CLI will
+     * determine the project from the current directory.
      */
     project: string;
     /**
-     * Do not create "spec.ts" test files for the new service.
+     * Skip the generation of a unit test file `spec.ts` for the service.
      */
     skipTests?: boolean;
 }

package/service/schema.json

@@ -4,11 +4,11 @@
   "title": "Angular Service Options Schema",
   "type": "object",
   "additionalProperties": false,
-  "description": "Creates a new, generic service definition in the given project.",
+  "description": "Creates a new service in your project. Services are used to encapsulate reusable logic, such as data access, API calls, or utility functions. This schematic simplifies the process of generating a new service with the necessary files and boilerplate code.",
   "properties": {
     "name": {
       "type": "string",
-      "description": "The name of the service.",
+      "description": "The name for the new service. This will be used to create the service's class and spec files (e.g., `my-service.service.ts` and `my-service.service.spec.ts`).",
       "$default": {
         "$source": "argv",
         "index": 0
@@ -20,12 +20,12 @@
       "$default": {
         "$source": "workingDirectory"
       },
-      "description": "The path at which to create the service, relative to the workspace root.",
+      "description": "The path where the service files should be created, relative to the workspace root. If not provided, the service will be created in the project's `src/app` directory.",
       "visible": false
     },
     "project": {
       "type": "string",
-      "description": "The name of the project.",
+      "description": "The name of the project where the service should be added. If not specified, the CLI will determine the project from the current directory.",
       "$default": {
         "$source": "projectName"
       }
@@ -33,11 +33,11 @@
     "flat": {
       "type": "boolean",
       "default": true,
-      "description": "When true (the default), creates files at the top level of the project."
+      "description": "Creates files at the top level of the project or the given path. If set to false, a new folder with the service's name will be created to contain the files."
     },
     "skipTests": {
       "type": "boolean",
-      "description": "Do not create \"spec.ts\" test files for the new service.",
+      "description": "Skip the generation of a unit test file `spec.ts` for the service.",
       "default": false
     }
   },

package/service-worker/schema.d.ts

@@ -1,13 +1,17 @@
 /**
- * Pass this schematic to the "run" command to create a service worker
+ * Adds a service worker to your project. Service workers enable your application to work
+ * offline or on low-quality networks by caching assets and intercepting network requests.
+ * This schematic configures your project to use a service worker.
  */
 export interface Schema {
     /**
-     * The name of the project.
+     * The name of the project to add the service worker to. If not specified, the CLI will
+     * determine the project from the current directory.
      */
     project: string;
     /**
-     * The target to apply service worker to.
+     * The build target to apply the service worker to. This is typically `build`, indicating
+     * that the service worker should be generated during the standard build process.
      */
     target?: string;
 }

package/service-worker/schema.json

@@ -4,18 +4,18 @@
   "title": "Angular Service Worker Options Schema",
   "type": "object",
   "additionalProperties": false,
-  "description": "Pass this schematic to the \"run\" command to create a service worker",
+  "description": "Adds a service worker to your project. Service workers enable your application to work offline or on low-quality networks by caching assets and intercepting network requests. This schematic configures your project to use a service worker.",
   "properties": {
     "project": {
       "type": "string",
-      "description": "The name of the project.",
+      "description": "The name of the project to add the service worker to. If not specified, the CLI will determine the project from the current directory.",
       "$default": {
         "$source": "projectName"
       }
     },
     "target": {
       "type": "string",
-      "description": "The target to apply service worker to.",
+      "description": "The build target to apply the service worker to. This is typically `build`, indicating that the service worker should be generated during the standard build process.",
       "default": "build"
     }
   },

package/ssr/schema.d.ts

@@ -1,15 +1,23 @@
+/**
+ * Enables Server-Side Rendering (SSR) for your Angular application. SSR allows your app to
+ * be rendered on the server, which can significantly improve its initial load performance
+ * and Search Engine Optimization (SEO). This schematic configures your project for SSR,
+ * generating the necessary files and making the required modifications to your project's
+ * structure.
+ */
 export interface Schema {
     /**
-     * The name of the project.
+     * The name of the project you want to enable SSR for.
      */
     project: string;
     /**
-     * Creates a server application using the Server Routing and App Engine APIs (Developer
-     * Preview).
+     * Configure the server application to use the Angular Server Routing API and App Engine
+     * APIs (currently in Developer Preview).
      */
     serverRouting?: boolean;
     /**
-     * Skip installing dependency packages.
+     * Skip the automatic installation of packages. You will need to manually install the
+     * dependencies later.
      */
     skipInstall?: boolean;
 }