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.

Specifies which AI tools to generate configuration files for. These file are used to improve the outputs of AI tools by following the best practices.

A collection of schematics to use in generating the initial application.

Configure the initial Git commit for the new repository.

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.

Disable interactive input prompts for options with a default.

The directory where the new workspace and project should be created. If not specified, the workspace will be created in the current directory.

Run through and reports activity without writing out results.

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).

Force overwriting of existing files.

Shows a help message for this command in the console.

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.

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.

Enable interactive input prompts.

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

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.

The package manager used to install dependencies.

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.

Enable routing in the initial application project. This sets up the necessary files and modules for managing navigation between different views in your application.

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.

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

Skip the generation of unit test files spec.ts.

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

Creates an application based upon the standalone API, without NgModules.

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

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

The unit testing runner to use.

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).

Create an initial application that does not utilize zone.js.