The name for the new application. This name will be used for the project directory and various identifiers throughout the application's code.

The file naming convention to use for generated files. The '2025' style guide (default) uses a concise format (e.g., app.ts for the root component), while the '2016' style guide includes the type in the file name (e.g., app.component.ts). For more information, see the Angular Style Guide (https://angular.dev/style-guide).

Include the styles for the root component directly within the app.component.ts file. Only CSS styles can be included inline. By default, a separate stylesheet file (e.g., app.component.css) is created.

Include the HTML template for the root component directly within the app.component.ts file. By default, a separate template file (e.g., app.component.html) is created.

Generate a minimal project without any testing frameworks. This is intended for learning purposes and simple experimentation, not for production applications.

A prefix to be added to the selectors of components generated within this application. For example, if the prefix is my-app and you generate a component named my-component, the selector will be my-app-my-component.

The directory where the new application's files will be created, relative to the workspace root. If not specified, the application will be created in a subfolder within the projects directory, using the application's name.

Generate an application with routing already configured. This sets up the necessary files and modules for managing navigation between different views in your application.

Skip the automatic installation of packages. You will need to manually install the dependencies later.

Do not add dependencies to the package.json file.

Skip the generation of a unit test files spec.ts.

Configure the application for Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering).

Create an application that utilizes the standalone API, eliminating the need for NgModules. This can simplify the structure of your application.

Enable stricter bundle budget settings for the application. This helps to keep your application's bundle size small and improve performance. For more information, see https://angular.dev/tools/cli/template-typecheck#strict-mode

The type of stylesheet files to be created for components in the application.

The unit testing runner to use.

Sets the view encapsulation mode for the application's components. This determines how component styles are scoped and applied.

Generate an application that does not use zone.js.