The Webpack skeleton doesn't use Gulp as its build system, but simply relies on NPM tasks. If you have a look at the scripts section in the package.json file, you'll see the list of tasks along with their corresponding command that can be run for the project. Here are the most common:
start: Launches a development web server. Whenindex.htmlis accessed for the first time, the application is bundled and served, and the process then watches the source files so it can recreate the bundles and refresh the browser when it detects a change. Thestartcommand is an alias forserver, which is itself an alias forserver:dev.test: Runs the unit tests. Code coverage is enabled using Istanbul (https://github.com/gotwarlost/istanbul).e2e: Runs the end-to-end tests. This task will launch both the application, which will run on port 19876, and the E2E test suite.build:prod: Bundles the application for production. The bundles and theindex.htmlfile will be optimized for production and will be generated in thedistfolder. Additionally, the production build will add a content-based hash to the name of each bundle, in order to version them. This has the same effect as enabling bundle revision by setting therevoption inaurelia_project/aurelia.jsonin CLI-based projects.server:prod: Launches a web server to serve the production bundle. It must be run afterbuild:prod.