Ember Cli Extension for Visual Studio Code
Use Ember and Ember Cli directly from Visual Studio Code. After installation, all
ember cli commands are available through Code's own command list, enabling you for example to generate blueprints, run tests, or build your app without leaving your editor. Also, IntelliSense for Ember!
- Visual Studio Code is automatically configured to play well with Ember Cli projects - as soon as a
.ember-cli file is detected in the workspace, we'll create a fitting
jsconfig.json to ensure that Visual Studio Code enables ES6 and Modules support.
- Typings to enable IntelliSense Support for Ember!
- All Ember Commands are available through Visual Studio Code's Command Palette.
- Snippets make day-to-day tasks a lot easier
- Create addon folder structure (also known as
- Build app (also known as
- Build, watch, and live-reload app (also known as
- Generate blueprint(also known as
- Destroy blueprint (also known as
- Create new app in the current workspace (also known as
- Create new app in a sub-folder in the current workspace (also known as
- Install ember addon (also known as
- Display the Ember Cli version (also known as
- Run tests (also known as
- Run tests in server mode (also known as
ember test --server)
- Setup project for development in Visual Studio Code
In Visual Studio Code, run
ext install vsc-ember-cli - or, simply hit
CMD/CTRL + Shift + P, search for "Install Extension", and then search for "ember cli".
Usage in subfolder
If your Ember app is within a subfolder of your workspace, you have to create an
ember.json file in the
.vscode folder of your workspace.
.vscode folder doesn't exist yet, you also have to create it.
After that you have to add a config that specifies the folder in which the Ember app resides.
The addon will do the regular setup (like creating a
jsconfig.json) as soon as the first command is executed.
Tip: There is a command to setup the project for Visual Studio Code.
Support is experimental - IntelliSense is enabled with typings, which are automatically installed in a
typings folder inside your project. The typings file should be automatically detected, but if not, you can either add it to your project's
jsconfig.json, or add a
/// reference to the typings in individual files.