Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Angular Design Patterns and Best Practices

You're reading from   Angular Design Patterns and Best Practices Create scalable and adaptable applications that grow to meet evolving user needs

Arrow left icon
Product type Paperback
Published in Feb 2024
Publisher Packt
ISBN-13 9781837631971
Length 270 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Alvaro Camillo Neto Alvaro Camillo Neto
Author Profile Icon Alvaro Camillo Neto
Alvaro Camillo Neto
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Part 1: Reinforcing the Foundations
2. Chapter 1: Starting Projects the Right Way FREE CHAPTER 3. Chapter 2: Organizing Your Application 4. Chapter 3: TypeScript Patterns for Angular 5. Chapter 4: Components and Pages 6. Chapter 5: Angular Services and the Singleton Pattern 7. Part 2: Leveraging Angular’s Capabilities
8. Chapter 6: Handling User Inputs: Forms 9. Chapter 7: Routes and Routers 10. Chapter 8: Improving Backend Integrations: the Interceptor Pattern 11. Chapter 9: Exploring Reactivity with RxJS 12. Part 3: Architecture and Deployment
13. Chapter 10: Design for Tests: Best Practices 14. Chapter 11: Micro Frontend with Angular Elements 15. Chapter 12: Packaging Everything – Best Practices for Deployment 16. Chapter 13: The Angular Renaissance 17. Index 18. Other Books You May Enjoy

Updating your project with the Angular CLI

The Angular framework is continually evolving with new features and optimizations, but to help communities and developers keep organized and their applications up to date, the Angular team uses semantic versioning to number their releases.

A semantic version number is composed of three parts and each part has the following representation:

  • Major: A number that is increased every time there is a change in the framework, which in turn requires us to change something in our application so that it continues to work, also known as a breaking change
  • Minor: A number that is increased when the new version has a new functionality that we can use, but if we don’t use it, we don’t need to change our application
  • Patch: A number that is increased when there is a correction to the framework and we do not need to change our code; this is widely used for versions that have security corrections

In this book, we are working...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime