All geek questions in one place

Any reasons not to use the Angular CLI to get started?

I am trying to decide if I should use the Angular CLI for a new project. My main reason for this is to avoid the trouble of setting up a new project right now and instead focus on learning the new Angular and building the application.

I come from Angular 1.x, so the cramps for me are associated with learning all new tools in addition to the new Angular. Most link systems are docs, but webpack seems like the direction the community is moving, so I would like to go that route.

I would rather study and become comfortable with the Angular toolchain (including webpack), but I would like to push it a bit, if possible. I usually do not prefer black boxes like the CLI.

I would like to start by using the CLI and then come off at some point in the future when I will have time to invest in learning more about webpack, etc. My question is: what limitations does the CLI make for me, can I easily tear myself away from it in the future, and in general, what else should I consider before using it as a quick way to get started?

+6
source share
2 answers

Angular 2, Alpha, , Angular -cli. - systemjs gulp , , .. Angular , , . ? . ? .

Angular -cli . Angular , Angular. , , . ng2 "ng new projectname --style = scss". "ng serve". . "ng build -prod -aot", ng2 Ahead of Time (aot) .

. ng2, , Angular -cli.

, angular2, ; , , ; Angular -cli.

+13

, , , , , CLI Angular 2.

CLI Angular - , NG2-Book CLI .

CLI Webpack CLI json, , 'ng eject' webpack ( ).

( ), CLI webpack Webpack .

0

Source: https://habr.com/ru/post/1015442/

More articles:


All Articles