I have read the first few chapters of the MEAP version of your book "Angular 2 Development with TypeScript", and also many of your responses here on Java Ranch. I see that you mention Angular CLI a lot, which I have heard of but have not used (yet). A colleague is using Angular Seed (https://mgechev.github.io/angular-seed/) in one of his projects, and I have taken a look at that "framework" (not sure what to call it). Can you please elaborate on what makes Angular CLI useful, and compare it to Angular Seed? Are these competing or complimentary?
Angular seed projects were offering a quick way to get started without the need to create several config files manually. We also created a couple of seed while writing our book. The repo for the book code samples (https://github.com/Farata/angular2typescript) has one for SystemJS-based projects (chapter2) and another for the manually-configured Webpack-based project (chapter10). Regardless of which seed project you use, you'll be following the author's view of how to develop with Angular.
But now Angiular CLI is a mature and standard way of jump-starting the project with all configurations and tools included. I don't see a need to use anyone's seen anymore. Go with Angular CLI. If you ever work on a really large project that requires fine tuning modularization or the bundling process, you'll invest time in learning the internals of Webpack or Rollup. But for most of the apps using Angular CLI works fine.
posted 3 years ago
Thank you very much for your response. I will check out Angular CLI soon.
What kind of corn soldier are you? And don't say "kernel" - that's only for this tiny ad: