drop grunt as our pseudo pipeline + build system about ember-cli

[joefiorini]

👍

[stefanpenner]

@joliss + me have next weekend planned to drive this one forward

[fsmanuel]

@stefanpenner after a discussion with @joliss about the use of broccoli I'm not sure if broccoli will replace grunt. or better to say that ember-cli has to fill in the gaps broccoli intentionally left.
How i get it is that ember-cli has to take some design and process decisions like

• before a build ember-cli removes the old dist folder
• a new build is located in the dist folder as a release (with a release number from package.json)
• etc.

In that process broccoli does the asset-pipeline step very well.

Open questions next to the process would be the integration of testem as a test runner (in ember-cli that would be the --autotest option and maybe a separate ember test command).

Concerning #11 and the discussion about conditionals in index.html offers broccoli a different approach that i haven't fully understood right now. I'll briefly highlight key conditionals in the Broccolifile.js.

• Add tests
• Uglify JavaScript
• Add bower files
• Add legacy files

What i don't understand yet is how to include specific files from lets say moment.js like language files. They should be all in the (bower)tree i guess and probably in the build what makes me think of load overhead. Maybe @joliss can shed some light on it.

Should i start a new issue with some checkboxes to have a discussion and talk about things i missed?

[stefanpenner]

so we are dropping grunt as the primary pipeline, as for the task runner we will bundle with, i am undecided.

grunt has been dropped as the build pipeline