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. In this example the Default TypeScript template was selected (marker 1) and the action continues with the Project configuration view (Image 4) as the consequence of the click on the
Next button (marker 2)
Image 4 shows the completed project's configuration, offering the choice between
Previous button and the
Next button - we will take that second choice (marker 1).
Now (Image 5), 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 (marker 1), by invoking npm API. This execution is triggered by the click on the Start button (Image 5). Note also that the
au run --watch task is also scheduled for execution once
npm install task finishes.
Image 6 depicts the task
npm install running for 4 seconds.
Finally, once the
au run --watch task is finished, you can close the Task manager, and click on the Chrome tile on the main view - resulting with the running app (Image 7)