#DEPRECATED You should now use the official ember-cli project!!!

Ember template for new apps using grunt

Heavily inspired by trek

Features

Easy to customize

It's just plain grunt!

No module system

No AMD, no CommonJS. Why? With frameworks like ember and angular you don't really need one. These frameworks already wrap everything in a function/class/module under a global namespace. Example: Ember.ArrayController.extend({ /* ... */ });
Instead we are using grunt-neuter to concatenate the files in the correct order.

It's fast

During development the concatenation and template compilation is instant. The production build takes a little while, because of the uglifing stuff.

Using ember production build

During development we are using the normal ember development build which provides us with great error messages. You do not want these in production so we are using the ember production version during the build process.

Tackling the Access-Control-Allow-Origin error during development

When starting the grunt server it is running on port 8000 and your backend server is running on a different port. So when you try to access your API you will get the Access-Control-Allow-Origin error in your browser. To avoid this error we are using a grunt proxy, which proxies every request back to your server. Take a look at the connect -> proxies section in the Gruntfile.js.

Live reload

Change a file, save it and your browser automatically reloads.

Setup

Install dependencies:

$ npm install .
$ npm install -g grunt-cli

Start a watch task and a live reload server at localhost:8000:

$ grunt
$ open http://localhost:8000/build/index.html

Run unittests from the console using phantomjs (additionaly you could start the watch task and open the test/testrunner.html in the browser):

$ grunt test

Production build:

$ grunt build

Upgrading ember

Replace the ember.js file with the debug version of ember.js. (There is a debug download link on emberjs.com)
Replace the ember.prod.js file with the minified version of ember.js. (There is a min + gzip download link on emberjs.com)
Make sure to use a handlebars version that is supported by your ember.js version.

Why do we use two files for ember.js?

The debug version contains some special error messages and assert-statements which are only useful during development and should not be in your production build. The ember build process removes these functions from the production build.

Upgrading handlebars

Replace handlebars.runtime.js with the latest runtime(!) build of handlebars. The download link is below the normal download button on handlebarsjs.com.
There is one small change we have to apply to the handlebars runtime. Normally I don't like changing external libraries, but it is only a small change in order to make it work with grunt-neuter:
Open the handlebars.runtime.js and at the top you should see the following line: var Handlebars = {}; replace this with window.Handlebars = {};. This basically just makes the handlebars object a global variable so that ember can find it.

Now we need to upgrade the grunt module which precompiles the handlebars templates:
Take a look at grunt-ember-templates history and find the version number which supports the handlebars version downloaded in the previous step.
In the package.json file update the version number of the grunt-ember-templates plugin.
Run npm install . and enjoy the latest version.

TODOS:

• Try out karma
• Maybe add htmlmin