Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Learning Angular
  • Toc
  • feedback
Learning Angular

Learning Angular

By : Aristeidis Bampakos
4 (6)
close
Learning Angular

Learning Angular

4 (6)
By: Aristeidis Bampakos

Overview of this book

Angular is an extremely fast, cross-platform JavaScript framework loved by millions. Learning Angular is a comprehensive introduction to the framework from an experienced Angular developer and Google Developer Expert. You’ll learn the Angular way of development as you build a real-world app from the ground up. Updated for Angular 19, this fifth edition tackles landmark changes in Angular after the “Angular Renaissance”. It covers app creation with standalone components, Angular Signals, and the new control flow syntax, while acknowledging differences in approach in older Angular code. You’ll also find a brand-new chapter on optimizing performance with SSR and hydration, as well as revamped content on TypeScript. Angular developers of all experience levels will benefit from this book. It is especially useful if you are new to Angular, as it will help you get to grips with the bare bones of the framework. By the end of this book, you'll be able to create Angular applications with TypeScript from scratch and apply best practices in any Angular codebase.
Table of Contents (15 chapters)
close
Free Chapter
1
Learning Angular, Fifth Edition: A practical guide to building web applications with modern Angular

Providing dependencies across the application

The Angular framework offers an actual injector that can introspect the tokens used to annotate the parameters in the constructor of an Angular artifact.

It returns a singleton instance of the type represented by each dependency so that we can use it straight away in the implementation of our class. The injector maintains a list of all dependencies that an Angular application needs. When a component or other artifact wants to use a dependency, the injector first checks to see if it has already created an instance of this dependency. If not, it creates a new one, returns it to the component, and keeps a copy for further use. The next time the same dependency is requested, it returns the copy previously created. But how does the injector know which dependencies an Angular application needs?

When we create an Angular service, we use the providedIn property of the @Injectable decorator to define how it is provided to the application. That is,...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete