Skip to content
Let’s prepare our main application gym diary to consume the micro frontend that we prepared previously. To do this, let’s start by creating a new module in the application. On the command line, we will use the following Angular CLI commands:ng g m exercise –routingng g c exercise/exercise With the preceding commands, we create the […]
With our micro frontend project ready, we need to prepare it to be consumed by another application. There are several ways to share micro frontends, from the simplest (and obsolete), with the use of iframes, to more modern, but complex, solutions such as module federation. In this section, we will use an approach widely used […]
As your application grows and becomes more complex, one team alone is not enough to maintain the growth rate, and new people are needed to handle other parts of the application as they appear. At this point, the architecture of your project needs to evolve, and one possibility is to divide your application into several […]
E2E tests aim to evaluate the system from the user’s point of view, simulating operations such as typing in a field, clicking on a button, carrying out the assertion, and evaluating the messages on the screen, just as a user would evaluate whether the action was successful or not. In the Angular ecosystem, in the […]
Angular component unit tests not only examine logic but also assess the values that will be presented on the screen. If your application follows the component architecture recommended by the Angular team (more details in Chapter 4, Components and Pages), you probably won’t have much business logic in your components, delegating it to services. To […]
Terms of Use | About yeagerback | Privacy Policy | Cookies | Accessibility Help | Contact yeagerback
