Initial buildout about ember-cli HOT 7 CLOSED

sounds great!

from ember-cli.

Got my answer, thanks. :)

from ember-cli.

So the plan is, drop in the EAK stuff, then refactor to Broccoli? Sounds good to me. @joefiorini if you want to help, try to avoid having stuff sitting in your local clone for too long - just send piecemeal PRs -, or we'll have merge conflict.

from ember-cli.

@joliss I was planning to separate the builder so we could have work going on the broccoli implementation throughout. To test it we can pass a flag, like: ember build --builder broccoli. This should minimize the risk of conflicts. As soon as I have it successfully building I'll open a PR so we can start communicating about it. Sound good?

from ember-cli.

Got some initial work going in my fork. So far I have ember build development and ember build production working (with minimal testing). I've started on ember server. What do you guys think of the direction I'm taking? At what point should I open a PR to get it merged in? @joliss @stefanpenner

from ember-cli.

Skimming the commits, I like the general direction. Let's not spend too much time on grunt, it's going away for sure.
PR: As quickly as possible, so we avoid conflicts. Partial progress is good. Just be sure to rewrite your history into something meaningful (git rebase -i), I'd like to avoid random "WIP" commits scattered about.

from ember-cli.

@joliss I usually don't like doing WIP commits, only pushed that one because I had a hard stop and wanted to share the direction I'm heading. Don't worry, it'll be gone soon.

As for grunt, the primary goal is to pull it in to get some structure in place and get a head-start on making it more configurable. That stuff should be the same regardless of the build system, right?

Do you have work done already on integrating this with broccoli?

from ember-cli.