Clever Geek Handbook

Use Angular-CLI or else use webpack for new Angular 4 projects

We've reached mid-2017 and the frontend has gone through a lot of updates, the most recent being the use of webpack on Angular-cli. I am going to work on a new Angular 4 project. Before I start, I want to get a community opinion on which between the two (Webpack or Angular-CLI) should be adopted for my project and why?

  • Is there an Angular-cli to which it can be used for large projects or is it still evolving?

  • If I opt for Angular-Cli, is there anything that can disable me later (limitations / features)?

  • Is Angular-cli appropriate and useful?

+3


source to share


1 answer


Update

My original answer is below, but outdated. Angular CLI now supports webpack.config

via ng eject

.



Original

  • Angular CLI uses Webpack to build / link project code.
  • Angular does not currently support CLI webpack.config

    ( and it looks like they are planning soon ), which could be a problem for your project on the line.
  • I don't understand why you couldn't start with Angular CLI and then drag and drop the project from it over time. The Angular CLI certainly makes working on a project easier.
+2


source






More articles:


All Articles