Angular Bootstrapping

Share This Post

In the last post, I introduced NgModule. NgModule is how an app’s pieces all fit and work together. Every Angular app has to have at least one NgModule. This is the core root module. Since it is the core root module, it launches the application/. We call this bootstrapping to launch the app. There are three cparts to NgModule.

Declarations Array

Whatever components are used in the NgModule need to be declared and thus added to the declarations array. This tells Angular that these components belong to this module. Additionally, since declarables are added here, you will find things like directives and pipes along with the declared components.

Note: declarables can only belong to a one module.

Imports Array

The imports array is where all dependent modules are placed.

Providers Array

The providers array holds all service dependencies.

NgModule Example

@NgModule({
  imports: [
    BrowserModule
  declarations: [
    AppComponent
  ],
  providers: [
    SomeService
  ],
  bootstrap: [AppComponent]
})

Now, while each Angular app contains at least one NgModule, I would encourage keeping separation of concerns in mind (SRP). You will find that a singular NgModule can get unwieldy quickly. So you will probably create multiple modules in an application.

Happy Coding!

Clay Hess

More To Explore

Code

Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.

Code

The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top
small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.