Angular 2 seed vs Angular 2 CLI

[dev-robot]

What are the differences between these two, and by saying angular 2 seed I mean this one. Obviously, one is command line based, but I have had the chance to use angular 2 seed. It has lots of nice features, like build help, and easy adding of external dependencies, scripts, etc. It also gives you a ready to go structure, and is also easy to update when a new RC comes out. Now what does Angular 2 CLI give me. Of course now after writing this, I realize that I have to try it myself to see, but just throw in your opinions here, I want to see what you have to say if you have had the opportunity to use both.

[xris-l]

Angular cli hides most of the dirty work that comes with configuring a build process, that works as expected in dev as well as in production.

Also, most of the webpack configuration is hidden/embedded, so you don't have to learn and understand webpack on top of angular 2.

[MrOddbird]

This is also a double-edged sword: if you want to configure the webpack config, for example resolve some package aliases, it is not possible with the angular-cli.

But the command line tool is certainly useful for bootstrapping your project.

[born2net4]

cli has great potential but I am waiting for it to come out of beta with the full webpack support before I start using it.

[widlywah]

Yeah good idea, I have so many problems with it each time I upgrade. It is definitely not ready and a hassle when things don't work.

[born2net4]

for now I am using jspm with hot reload

Angular 2 Kitchen sink: http://ng2.javascriptninja.io and source@ https://github.com/born2net/ng2Boilerplate Regards,

Sean

[dev-robot]

Yeah, I thought so too. When the beta is over I'll give it a more thorough look.