In the app's current state, the entire page refreshes when we click on an internal link that exists within the app. While this may not seem significant with a small app, this can have performance implications for larger pages with more content where users have to redownload assets and run calculations again.
Note: Learn more about adding routes to your application in the in-depth guide.
In this activity, you'll learn how to leverage the RouterLink directive to make the most use of Angular Router.
- 
      
      
  
Import
RouterLinkdirectiveIn
app.tsadd theRouterLinkdirective import to the existing import statement from@angular/routerand add it to theimportsarray of your component decorator....import { RouterLink, RouterOutlet } from '@angular/router';@Component({ imports: [RouterLink, RouterOutlet], ...}) - 
      
      
  
Add a
routerLinkto templateTo use the
RouterLinkdirective, replace thehrefattributes withrouterLink. Update the template with this change.import { RouterLink, RouterOutlet } from '@angular/router';@Component({ ... template: ` ... <a routerLink="/">Home</a> <a routerLink="/user">User</a> ... `, imports: [RouterLink, RouterOutlet],}) 
When you click on the links in the navigation now, you should not see any blinking and only the content of the page itself (i.e., router-outlet) being changed 🎉
Great job learning about routing with Angular. This is just the surface of the Router API, to learn more check out the Angular Router Documentation.