ANGULAR VERSIONS DIAGRAM HOW TO

Changing requirements - how can we keep up with the demands of the business to continually update the application without letting technical debt get out of control?.Increased size and complexity - how can we structure our code so that it can grow without sacrificing clarity or performance?.Safety - how do we ensure that our code will not be subject to attacks or prone to errors?.

Consistency - how do we make sure everyone in the organization (which may be thousands of people) follows the same best practices for structuring and writing code?.

We can summarize the concerns of enterprise teams like this: This means they’ll need to do as much work as possible at the beginning of an application’s development to minimize the cost of maintenance down the road. In addition, enterprise teams need to assume that their code will stick around for many years to come. While small groups might be able to get away with ad hoc decisions on application structure or coding best practices, the same cannot be said when you’re working with dozens or perhaps hundreds of other people. Concerns of Enterprise Teamsĭeveloping applications on a large enterprise team is different than developing alone or on a small team. If you've never touched Angular before, check out our Real World Angular series. Note: This tutorial assumes some basic knowledge of Angular and the Angular CLI. You can see the finished code in this repository.

ANGULAR VERSIONS DIAGRAM HOW TO

TL DR In this tutorial, we’re going to learn the basics of Nrwl’s tool Nx, as well as how to create a custom workspace CLI schematic.

Angular versions diagram