This initial preview is very limited when compared with our plans for Monterey. It is also quite capable already, when used to replace the most likely Aurelia application development workflow which is based on the Sublime-like text editor, console and a browser, starting from skeleton-esnext template. As explained in the related README.md document, you would start by creating the local copy of the that template and issue a series of commands in the console, invoking CLI tools like ‘npm’, jspm’ and ‘gulp’ and using tools like BrowserSync invoked by Gulp scripts.
Monterey does this same job in a lot more user friendly way, via modern GUI as shown next using the skeleton-esnext template. These screenshots and their sequence should be self-explanatory. There are some added comments where that is not true.
While the above 7 screenshots illustrate the full “create, build and run” cycle, this is a small fraction of Monterey’s abilities. We have built already some of the tools like NPM and JSPM manager, which can be used in many different scenarios (yet to be implemented, though)
Subsequent versions will add more package managers and module loaders and the workflows needed to support tasks like
- upgrade an Aurelia app to the next version of the Aurelia framework
- convert an aurelia app from using JSPM loader to use Webpack loader
- analyze compatibility of Aurelia framework modules version with third party modules.
All these projections of the future (see possible future plans for Monterey for more details) are just that – projections.
Did you like this article? Would you like to see any other “brief story” about Monterey? Give us your feedback here or in the comments form below.