ng new

Creates a new workspace and an initial Angular application.

ng new <name> [options]

ng n <name> [options]


Creates and initializes a new Angular application that is the default project for a new workspace.

Provides interactive prompts for optional configuration, such as adding routing support. All prompts can safely be allowed to default.

  • The new workspace folder is given the specified project name, and contains configuration files at the top level.

  • By default, the files for a new initial application (with the same name as the workspace) are placed in the src/ subfolder. Corresponding end-to-end tests are placed in the e2e/ subfolder.

  • The new application's configuration appears in the projects section of the angular.json workspace configuration file, under its project name.

  • Subsequent applications that you generate in the workspace reside in the projects/ subfolder.

If you plan to have multiple applications in the workspace, you can create an empty workspace by setting the --createApplication option to false. You can then use ng generate application to create an initial application. This allows a workspace name different from the initial app name, and ensures that all applications reside in the /projects subfolder, matching the structure of the configuration file.


Argument Description

The name of the new workspace and initial project.


Option Description

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

Aliases: -c


Initial git repository commit information.

Default: true


When true (the default), creates a new initial application project in the src folder of the new workspace. When false, creates an empty workspace with no initial app. You can then use the generate application command so that all apps are created in the projects folder.

Default: true


When true, disables interactive input prompts for options with a default.


The directory name to create the workspace in.


When true, runs through and reports activity without writing out results.

Default: false

Aliases: -d


When true, forces overwriting of existing files.

Default: false

Aliases: -f

--help= true|false|json|JSON

Shows a help message for this command in the console.

Default: false


When true, includes styles inline in the component TS file. By default, an external styles file is created and referenced in the component TS file.

Aliases: -s


When true, includes template inline in the component TS file. By default, an external template file is created and referenced in the component TS file.

Aliases: -t


When false, disables interactive input prompts.


Add support for legacy browsers like Internet Explorer using differential loading.

Default: false


When true, creates a workspace without any testing frameworks. (Use for learning purposes only.)

Default: false


The path where new projects will be created, relative to the new workspace root.

Default: projects

--packageManager= npm|yarn|pnpm|cnpm

The package manager used to install dependencies.


The prefix to apply to generated selectors for the initial project.

Default: app

Aliases: -p


When true, generates a routing module for the initial project.


When true, does not initialize a git repository.

Default: false

Aliases: -g


When true, does not install dependency packages.

Default: false


When true, does not generate "spec.ts" test files for the new project.

Default: false

Aliases: -S


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.io/strict

Default: false

--style= css|scss|sass|less|styl

The file extension or preprocessor to use for style files.


When true, adds more details to output logging.

Default: false

Aliases: -v

--viewEncapsulation= Emulated|Native|None|ShadowDom

The view encapsulation strategy to use in the initial project.

© 2010–2020 Google, Inc.
Licensed under the Creative Commons Attribution License 4.0.