JavaScript Other
Latest commit 23be4fb Mar 28, 2017 @homu homu Auto merge of #6907 - elwayman02:ignore-ember-try, r=Turbo87
Ignore files created by Ember-Try

Ember-Try creates a number of temporary files within a project during its test runs. This can cause IDEs & Version Control Tools to try and scan the files, which uses unnecessary resources on the system. Additionally, if Ember-Try exits unexpectedly, some of these files may not be cleaned up correctly, leaving them around to be accidentally committed.

Adding these files to `.gitignore` will alleviate both problems, given the intentional temporary nature of the files.
Failed to load latest commit information.
.github include global npm version Sep 2, 2016
.travis Auto merge of #6584 - ember-cli:allow-experiments-only-on-canary, r=n… Dec 20, 2016
assets/architecture enforce styles, clean up whitespace and extra lines Oct 30, 2015
bin Move instrumentation out of `bin/ember`. (#6801) Feb 21, 2017
blueprints Auto merge of #6907 - elwayman02:ignore-ember-try, r=Turbo87 Mar 28, 2017
dev Merge branch 'beta' Jan 18, 2017
docs ESLint: Enable "no-multi-spaces" rule Jan 4, 2017
lib add yuidocs for the addon:init method Mar 28, 2017
tests Fix linting error Mar 27, 2017
.codeclimate.yml Add Code Climate config May 23, 2015
.editorconfig remove application.hbs newline Jan 29, 2017
.eslintignore ESLint: Add "no-undef" rule Feb 12, 2016
.eslintrc.js Use babel@6 internally. Mar 12, 2017
.gitattributes use eol=lf for windows Jan 13, 2016
.gitignore Update to npm 3 Sep 29, 2016
.npmignore Removing jshint reference in blueprints Jan 12, 2017
.travis.yml Remove support for Node 0.12. Dec 31, 2016 Use secure URLs in docs where possible Oct 17, 2016 Removing jshint reference in blueprints Jan 12, 2017 Release v2.13.0-beta.2 Mar 22, 2017 Fix code of conduct markdown formatting Jul 21, 2015 Update to reference latest Node LTS. Dec 31, 2016
LICENSE [DOC] Update license year Jan 1, 2017 Tweaked PERF_GUIDE instructions (#6750) Feb 7, 2017 Use secure URLs in docs where possible Oct 17, 2016 Auto merge of #6699 - Turbo87:copypasta, r=rwjblue Jan 18, 2017 Add a sourcemaps doc Nov 29, 2016 Fix typo in transition doc Sep 12, 2015
appveyor.yml AppVeyor: Install NPM 3 Jan 16, 2017
package.json Auto merge of #6890 - rwwagner90:dag, r=Turbo87 Mar 24, 2017
yarn.lock Auto merge of #6890 - rwwagner90:dag, r=Turbo87 Mar 24, 2017


Latest NPM release TravisCI Build Status AppVeyor Build Status Test Coverage Code Climate

The Ember.js command line utility.


  • Asset build pipeline using Broccoli.js
  • ES6 transpilation using Babel
  • Project structure conventions using ES6 module syntax
  • Development server including live-reload and API proxy
  • File/Project generator using blueprints
  • Unit, Integration and Acceptance test support using Testem
  • Powerful addon system for extensibility


npm install -g ember-cli


After installation the ember CLI tool will be available to you. It is the entrypoint for all the functionality mentioned above.

You can call ember <command> --help to find out more about all of the following commands or visit to read the in-depth documentation.

Create a new project

ember new my-new-app

This will create a new folder my-new-app, initialize a Git project in it, add the basic Ember.js project structure and install any necessary NPM and Bower dependencies.

Create a new addon project

ember addon my-new-addon

This is essentially similar to ember new but will generate the structure for an ember-cli addon instead.

Build the project

ember build

This will create a dist folder and run the build pipeline to generate all the output files in it. You can specify --environment=production to build in production mode, which includes code minification and other optimizations.

Run the development server

ember serve

This will launch a development server that will automatically rebuild your project on file changes and serves the built app at http://localhost:4200/.

Run the test suite

ember test

This command will start the Testem runner, which will run all your tests from the tests folder. This command also supports a --server option which will automatically run tests on file changes.

Generate files

ember generate route foo

This will generate a route named foo. route is an example here and can be replaced by any other available blueprint. Blueprints are provided by ember-cli itself and any of you installed addons. Run ember generate --help to see a list of available blueprints in your project and their options.

Install an ember-cli addon

ember install some-other-addon

This will search NPM for a package named some-other-addon, install it and run any additional install steps defined in the addon.



Start by cloning the Git project to your local hard drive:

git clone

Link ember to your development version

Running the following command will link the global ember utility to your local development version:

npm link

Note that the global ember CLI utility will automatically relay to any project-local ember-cli installation. If you want to use your development version there instead run the following command from your Ember.js project folder:

npm link ember-cli

Read the official npm-link documentation for more information.

Run the test suite

npm test

will run ESLint and the "fast" subset of the test suite. Run npm run test-all for the full test suite which will currently take quite a few minutes due to heavy IO and network usage.

ember-cli is using Mocha for its internal tests. If you want to run a specific subset of tests have a look at their documentation.

Build the documentation

Use npm run docs to build HTML and JSON documentation with YUIDoc and place it in docs/build/. Please help by improving this documentation.


This project is licensed under the MIT License.