This doesn’t have to be done in one go either, because Standalone Components play wonderfully together with Angular modules. This strategy also seems smug at first glance: You simply remove all Angular modules from your source code. Option 2: Just Throw Away Angular Modules You can therefore safely ignore Standalone Components or only use this new option in new applications or application parts. After all, the entire ecosystem is based on it. Angular will continue to support Angular modules. Nobody is forcing us to convert applications to Standalone Components. Stick your head in the sand and ignore everything around you:Įven if that sounds smug, there is actually nothing wrong with it. Let’s start with the simplest option – the ostrich strategy. In this article I show four options to do so. Now the question arises how to prepare an existing Angular solution for a future without Angular modules. As they are self-contained and don’t need NgModules, application become more lightweight. In the last article of this series, we discussed Standalone Components planned for future Angular releases. Automatic Migration to Standalone Components in 3 Steps.The Refurbished HttpClient in Angular 15 – Standalone APIs and Functional Interceptors.Angular Elements: Web Components with Standalone Components.Routing and Lazy Loading with Angular’s Standalone Components.4 Ways to Prepare for Angular’s Upcoming Standalone Components.Angular’s Future Without NgModules – Part 2: What Does That Mean for Our Architecture?.
0 Comments
Leave a Reply. |