In its first release, Monterey addresses some of the tooling issues, trying to balance the usefulness with “time to market” (Aurelia Tools team is very small and needs to chose the features set for each subsequent release very carefully in order to create a steady stream of useful innovations). So it should not be a surprise that Monterey’s primary focus is on creating new applications – with special accent on using Aurelia-CLI tool. This decision was not made easy particularly because Aurelia-CLI is very new and because it supports only RequireJS module loader, at the time when most existing Aurelia applications are SystemJS module loader based. However, we are very committed to sharing Aurelia core team’s vision so providing full scaffolding based on Aurelia CLI was a good start.
Aurelia-CLI is not frozen in time (it is really just in Alpha stage) so we can all expect support for other module loaders and many features we do not know about – which is another reason why Monterey application scaffolding feature could be viewed as a visual shell on top of Aurelia-CLI.
In order to help developers with existing applications, Monterey offers graphical views of configuration data (NPM Package Manager, JSPM Package Manager), collection of plugins (aka features) that help with the integration of tools that developers use in their daily workflows and the support for creating new applications from the Aurelia application skeletons. In this context, Monterey reaches wider than supporting just the RequireJS module loader, following the same steps Aurelia introduced so far.
The important fact to remember is that Monterey is in its infancy and that we plan to make it as powerful / useful as our resources allow us and in order that our initial users will suggest to us. This is why it is important that you fill in the survey (at the end of the Introducing Monterey blog article) or share your opinions with us as either comments to this blog article or in this Gitter chat room.