Allow you to launch Angular schematics CLI commands from files Explorer or Command Palette in Visual Studio Code.
Switch branches/tags
Clone or download

Angular schematics extension for Visual Studio Code

Visual Studio Code extension allowing you to launch Angular schematics (CLI commands) with a Graphical User Interface, directly inside VS Code!



  • Save time
  • No more typo errors = no more mess cleaning
  • No more chaotic search in the CLI wiki, all options available will be proposed and documented
  • Promote good practices for component types

What about other tools like the Angular Console? Well, this lib will save you more time because:

  • it's directly integrated in VS Code (no switch between 2 windows),
  • many options are prefilled (like the path and the project where you want to generate things),
  • generated files will auto open!

By the same author

Getting started

Follow instructions on Visual Studio Code marketplace, or just search for "Angular schematics" by "Cyrille Tuzi" directly inside VS Code extensions panel.

Then, you can launch Angular CLI commands from 3 places:

  • the files Explorer context menu: right-click on any directory or file, then choose an "Angular: Generate..." command
  • the dedicated Angular Schematics view (icon in the Activity bar on the left)
  • or the Command Palette

And finally just fill the requested options.

The quickest way to launch your Angular CLI commands is the first, with a right-click inside the files Explorer context menu. Why? Because the destination path will be automatically configured to the directory you just right-clicked.


VS Code

This extension requires VS Code >=1.24.

Angular CLI

This extension is only enabled inside an Angular >=5 CLI project, ie.:

  • with @angular/cli >=1.7 or >=6 installed globally,
  • with an angular.json or .angular-cli.json file in workspace (automatically done by the CLI).

The project opened must be the root directory of the Angular project. It won't work from a parent directory, as the CLI itself requires to be in the Angular directory.

Path automatic detection

The path automatic detection only works if you stick to official CLI structure, meaning you must be in:

  • /**/app/ (like /src/app/)
  • /projects/**/**/app/ (like /projects/someotherapp/src/app/)
  • /projects/**/**/lib/ (like /projects/somelibrary/src/lib/)
  • /projects/**/**/**/lib/ (like /projects/company/somelibrary/src/lib/ for scoped @company/somelibrary)

Custom shell

On macOS or Linux, if you use a custom shell (like zsh) and your Angular CLI installation is tied it, it must be configured accordingly in your VS Code settings ( or

Other features

Other schematics

By default, this extension supports (if they are installed):

  • @schematics/angular (official Angular CLI commands)
  • @angular/material
  • @ionic/angular-toolkit
  • @ngrx/schematics
  • @nrwl/schematics
  • @nstudio/schematics

Scanning all packages to find all potential schematics would be too slow. If you want to use other schematics, just add their package name in ngschematics.schematics in your VS Code preferences.

For example: "ngschematics.schematics": ["@angular/material"]

If you are a library author, feel free to open an issue to ask for your schematics to be added in the default list.

Keyboard shortcuts

You can add keyboard shortcuts to the following actions:

  • ngschematics.generateComponent
  • ngschematics.generateService
  • ngschematics.generateModule
  • ngschematics.generate

Default options

schematics option of angular.json already allows to save default options for schematics commands.


The icons in the Angular Schematics view will be nicer if you use the Material Icon Theme extension.

Component types

Puzzled about the component type choice?

Exported component

Components have a local scope by default, meaning they are only usable inside the module where they are declared. So if you want to use your component in another module (for example if you are doing a reusable UI component), you have to export it. Learn more about Angular modules and their scopes.

Pure component (also known as a presentation component)

A pure component is a component which relies only on its @Inputs for data, as opposed to an impure component, which relies on external asynchronous operations (like a HTTP request via a service) for data. Observing this difference is a good practice, learn more about architecture in Angular projects.

Element component

Only available in Angular >= 7.

Used to create an Angular Element, i.e. a reusable native Web Component. Such components need to be registered in entryComponents and to use native ShadowDom viewEncapsulation. See the documentation for more info.

Release Notes

Changelog available here.