Like any other Aurelia module, you import and inject it into your view model before using it. Hopefully it is now more clear what Im doing wrong.

First, aurelia-cli is not a standard scaffolding system. Well, these are true for Aurelia framework, but not for the suggested build systems. The Event Aggregator only has three exposed methods and they are incredibly easy to understand. Kudos go to stoffeastrom from the Aurelia gitter channel who actually pointed out the right direction. Probably the most important two reasons why Aurelia has a big competitive advantage over other frameworks are: 1) Convention over Configuration 2) Strive for standards. They are not essential, they are like observers, when something happens the subscriber methods are notified and allow you to act accordingly.Įverything comes with a cost, so don’t abuse it and use it for every change in your application, it is very much for those situations where cross component communication is essential. It allows you to fire off events that don’t have a specific target, events potentially multiple listeners could be looking out for. If your application requires knowing about what other parts are doing at various times in your application, the Event Aggregator can be incredibly helpful. Like choosing to use anything, the decision to use the Event Aggregator module should be dictated by your application requirements. This works with latest aurelia & bootstrap (as of 2018-Feb) without using the prepend method. I cannot find samples regarding Aurelia CLI with Require.js. Aurelia is a next gen JavaScript client framework for mobile, desktop and web that leverages simple conventions to empower your creativity.

In my experience, the default conventions will meet your needs nine out of ten times. So does a search on both Aurelias Gitter.im channel and on StackOverflow. If you’re not sure what that means, it means by default Aurelia makes some assumptions about how you want your application to work. The Aurelia Gitter channel has 3,665 members at the time of this writing with almost 300,000 messages. The explosion in community involvement continues to amaze me. If you look at the source of this module for Aurelia, you will see it is actually super simple to understand and how it works. Convention over configuration This might come down to personal taste, but Aurelia takes a convention over configuration approach. The Aurelia framework was only announced a year and a half ago.

At its core the Event Aggregator is a pub/sub layer for publishing and listening to actions that take place inside of your application loosely. Also, In my project input controls are not kept directly on the fluent.html (as shown in the sample app) but on a nested level to load entities dynamically with. I have instantiated them inside attached () method. But I have noticed people ask about it in the Gitter chat from time-to-time. Is it necessary to instantiate the reporter and observer in the constructor of the view model. There does not seem to be much info out there about it, probably due to its simplicity. The Event Aggregator is one of my favourite things about Aurelia and it is not even anything unique to Aurelia.