Modules

This prompt lets us choose additional third-party modules from the JHipster marketplace (https://www.jhipster.tech/modules/marketplace). This can be helpful if we want to use additional features not supported directly by JHipster. We will look at this in later chapters. For now, let's choose No. Don't worry about this, as these modules can be added to the application later when required as well:

Once all the questions are answered, the code generation will start and you will see an output like following, listing the files created, and then running yarn installation to get all the frontend dependencies installed.

If you do not want the Yarn install and Webpack build steps to run, you could use the --skip-install flag while running JHipster to skip this. Just run jhipster --skip-install

Once the installation is complete, the generator will trigger a webpack build for the client side so that when we start the application, we have everything ready:

JHipster will check your environment to see if all the required dependencies like Java8, NodeJS, Git, and NPM/Yarn are installed. If not, it will show friendly warning messages before code generation starts.

Once the process is complete, you will see successful messages as follows, and instructions to start the application:

There are command-line flags that can be passed while executing the jhipster command. Running jhipster app --help will list all of the available command-line flags. One of the interesting flags, for example, is npm, which lets you use NPM instead of Yarn for dependency management.

JHipster will automatically initialize a Git repository for the folder and commit the generated file.  If you wish to do this step yourself, you can do so by passing the skip-git flag during executing jhipster --skip-git and execute the steps manually as follows:

> git init
> git add --all
> git commit -am "generated online store application"

You could also use a GUI tool like Sourcetree or GitKraken if you wish to do so to work with Git.