Creating new application | Aurelia-CLI
Like all Monterey application creation wizards, the process starts with the definition of the location where the application will be persisted (Image 1). Note the red "number-markers" which indicate the sequence of mouse click needed to invoke the Files Explorer, select the folder and move to the wizard's next step.
The next required data is the definition of the application's name (Image 2). This is the name that will appear on the Monterey's list-view of all open applications. Since this same name will be used as the name of the folder where the application "lives", this name needs to be unique. Observe that Monterey verifies each proposed application name for uniqueness.
At this point (Image 3) the user is asked to choose between the several Aurelia-CLI templates (three at the time of writing this document; this number will increase as the Aurelia-CLI command line tool evolves.
The selected "Default ESNext" template is completely defined at this point and Monterey creates the Project configuration summary page (Image 4). You can go back through all steps that led to the Project configuration definition, if you realize that some of the specifications in any of these previous steps are not correct
At this point we reached the most important step of the Monterey wizard - page where will eventually reside the Monterey workflow plugin. At this time you see the workflow's "place-holder" implemented as a list of check-boxes presenting the list of application build options that are meaningful in the given context. As Monterey gets able to handle a lot more complex tasks (managing creation, building, testing and deployment tasks of several tens of applications at the same time, the concept of the "workflow of workflows" will be the best way to ensure correct and meaningful definition of all of these tasks running in a conflict-free fashion.
The concrete example here is very simple: run the equivalence of
npm install and
jspm install tasks executed in the serial fashion in the console, by invoking npm and jspm API. This execution is triggered by the click on the
Start button (Image 5)
Click on the
Start button on Image 5 above causes the switch of the Monterey's view - from the "workflow" to the Monterey Task manager (Image 6). This is the most often used Monterey integrated tool, which is the controlling and management entity for handling all running Monterey applications. At this time we have a single application (
Default-ESNext) running, and you can see that the currently running task is
NPM install, which will be followed by two more tasks. You can also see the embedded console showing the line-by-line progress of the currently running .
NPM install task.
Note that Monterey is designed to be able to run many tasks in parallel - this view is restricted to show only the information for the selected project (