Ember CLI is the official command line utility used to create, build, serve, and test Ember.js apps and addons.
It provides a consistent project structure, a powerful addon system, and a fast Broccoli-powered build pipeline. Whether you are looking for a zero-config experience or the ability to make your own customizations, Ember CLI has the tools you need.
Ember CLI’s asset compilation system has out-of-the-box support for:
Using a custom resolver, Ember CLI can automatically import modules when
needed. For example, the route in
routes/post.js will know to use the
controllers/post.js and the template in
You are not limited to automatic resolution so if your application needs to
explicitly include a module, it’s only an
import away. Learn more about
ES2015 modules here.
Testing using the CLI
Ember CLI’s runtime is configurable via a file named
JSON-formatted file, which must be placed in your home directory, can include
any command-line options whose names must be in camel case form. For example:
Content Security Policy
When enabled, Content Security Policy headers help mitigate certain types of
attacks including Cross Site Scripting (XSS) and data injection.
Browser support is very good,
ember-cli-content-security-policy addon makes it easy to build your
app with CSP in mind. For example, enabling it on your production stack is
a matter of adding headers.
Ember CLI is continuously evolving. It’s an on-going community effort. We welcome your issues and PRs for features, bug fixes, and anything that would improve your quality of life as an Ember developer.
Talk to us here:
Currently, Ember CLI supports Node (latest LTS recommended), npm (3.x and above) or yarn.