Creating new application
skeleton-esnext-webpack
Note the red "number-markers" which indicate the sequence of mouse clicks.
Start by selecting the template skeleton-esnext-webpack(Image 1, marker 1).Then continue with the definition of the location where the application will be persisted (marker 2). This action will invoke the Files Explorer, where you have to define the folder (marker 3) and click on the Select folder button to define the location where the application will be stored.
Image 1
Having defined the path to the folder where the application is stored, click one the Next button (marker 1, Image 2)
Image 2
Image 3 shows the completed project's configuration, offering the choice between Previous button and the Next button - we will take that second choice (marker 1).
Image 3
Now (Image 4), 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), and npm start by invoking npm API (action different from invoking the same service using the console). This execution is triggered by the click on the Start button (marker 2).
Image 4
Image 5 shows the Task manager indicating the task NPM install being executed (running for 13 seconds so far) and the embedded console provides the npm streaming log.
Image 5
At this point the application build process reached the npm start step, which invoked the Webpack loader to start the application, running at the port 9000.
Image 6
Pointing the browser to http://localhost:9000 results with expected outcome:
Image 7