{"id":615,"date":"2023-03-07T05:00:00","date_gmt":"2023-03-07T13:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=615"},"modified":"2023-03-04T12:11:43","modified_gmt":"2023-03-04T20:11:43","slug":"standalone-application-and-router-config","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/standalone-application-and-router-config\/","title":{"rendered":"Standalone Application and Router config"},"content":{"rendered":"\n

With this daily post, let’s get back to the new Angular standalone features. So far, we have seen how to create standalone components, add dependencies<\/a>, and lazy-loading<\/a> of standalone components.<\/p>\n\n\n\n

Since the primary goal of standalone components is to have less NgModules<\/code>, what about creating an Angular application with no NgModule<\/code> at all?<\/p>\n\n\n\n

Enter the bootstrapApplication<\/a><\/code> function (from @angular\/platform-browser<\/code>). All it needs is the root standalone AppComponent<\/code> as a parameter:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

And that’s it. No AppModule<\/code> needed. Now you’re probably wondering: How to add some router config?<\/p>\n\n\n\n

There’s a provideRouter<\/a><\/code> function for that, along with several router utility functions<\/a> to configure preloading, guards, error handling, and more<\/a>:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

Last but not least, if you need to use services from a third-party module and don’t want to import the other features of that module (components\/pipes\/directives), you can also do the following:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

As you can see, standalone components have paved the way for many new function-based features (instead of classes\/services), and we’ll see even more of those in the coming posts.<\/p>\n","protected":false},"excerpt":{"rendered":"

With this daily post, let’s get back to the new Angular standalone features. So far, we have seen how to create standalone components, add dependencies, and lazy-loading of standalone components. Since the primary goal of standalone components is to have less NgModules, what about creating an Angular application with no NgModule at all? Enter the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,21,25,23],"tags":[],"class_list":["post-615","post","type-post","status-publish","format-standard","hentry","category-angular","category-architecture","category-routing","category-standalone"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t